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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds genuinely new behavioral facts: retrieval is free, it re-runs current access checks at call time, and it replays the exact previously paid response rather than generating new content. It does not describe failure behavior when the operation is not owned/ready.

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 tight sentences, front-loaded with the primary action and followed by the scoping/billing caveat. The second sentence is slightly list-y ('not a new page, fresh observation or additional charge') but each clause disambiguates against a real alternative behavior.

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?

Output schema exists, so return-value shape need not be explained, and for a one-parameter tool the description covers the key gating conditions and the billing implication. Remaining gap is error/edge handling when the operation is not owned, not ready, or no longer accessible.

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% for the single operation_id parameter, so the description must compensate. It indirectly constrains the id (it must reference an operation you own that is in a 'ready' state), but says nothing about the UUID format or how to obtain the id.

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 ('Return') and a precisely qualified resource ('an owned ready operation's exact previously paid response'), which is enough to distinguish it from get_research_status (status vs. payload) and from any fresh-observation tool. It does not name a sibling explicitly, so it stops short of a 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?

Gives the selecting context clearly — only for an operation you own that is 'ready' and already paid — and excludes misuse by stating it is 'not a new page, fresh observation or additional charge'. No alternative sibling is named for the case where the operation isn't ready or wasn't paid, so it lacks the explicit routing a 5 requires.

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