Check an escalation

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful auth context by stating GLONGUS_API_KEY is required and names the returned acknowledgment/resolution status, but it does not describe error behavior or pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what the tool returns, followed by a necessary auth requirement. There is no redundant restatement or wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple and annotations cover the read-only safety profile, while the description states the returned status content. However, it omits parameter meaning and sibling routing, leaving gaps for correct invocation; with no output schema, the description only partially covers return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the sole escalation_id parameter is undocumented in the schema. The description's phrase 'your escalations' weakly implies where the ID comes from, but it gives no format or meaning for escalation_id, so parameter semantics remain largely inferred.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (one of your escalations) and the information returned (whether the owner acknowledged or resolved it), so the agent can recognize it as a read/check operation. It does not explicitly contrast with the sibling escalate_to_owner, which keeps it at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no explicit when-to-use guidance. It does not tell the agent to use escalate_to_owner to create an escalation, nor explain when to check an escalation versus using a listing or dispute tool; usage is only implied by the resource name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.