supportpages_get_operation

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

Annotations already declare the safe read profile, and the description adds real behavioral context beyond them: it never resubmits work, it recovers the most recent request when operation_id is omitted, and polling is bounded to 20 seconds. Return format and exact wait semantics remain unspecified, but the added context is strong.

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?

Front-loaded with the core action, then usage, then a caveat, then recovery behavior. Dense but every sentence adds a distinct constraint. Slightly compressed given multiple clauses per sentence.

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?

An output schema exists so return values need no explanation, and annotations cover the safety profile. The description covers purpose, timing, exclusions, and recovery, leaving only the workspace parameter and precise wait behavior unaddressed.

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 coverage is 0%, so the description must carry parameter meaning. It explains operation_id well (use the saved id, or omit it to recover the most recent request) and indirectly touches wait_ms via 'polling is bounded to 20 seconds,' but says nothing about the workspace parameter. Partial compensation only.

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?

States a specific verb+resource: 'Check a hosted operation once.' The clause 'it never resubmits work' implicitly distinguishes it from the retry/update siblings, though no sibling is named explicitly. An agent can tell what it reads without opening the schema.

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?

Gives explicit triggers ('when the user asks how it is going or after a client restart') and an explicit prohibition ('Do not call it on a loop while an operation runs'), plus the reason (the review link shows live progress). Clear when-to and when-not guidance.

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