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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so safety is covered; the description adds real value by saying the original query settings are preserved and that the continuation_id must be one the prior result returned. It stops short of describing what happens with an expired or invalid continuation_id, which is the one behavior an agent could trip over.

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?

Three short sentences, front-loaded with the action, then the required inputs, then the usage decision and the sibling exclusion. No filler and nothing repeated from the schema.

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 not be described, and the annotations cover the safety profile; the description supplies the continuation precondition and the get_transcript alternative. The remaining gap is failure handling for stale or mismatched continuation_id, which would matter for an agent recovering from an error.

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 the load, and it does: result_id is tied to a previous result and continuation_id is constrained to 'one returned' by that result. It does not add format or validity details (string shape, expiry), leaving a small gap, but the meaning of both parameters is clear.

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 (retrieve) and resource (the next page / additional detail / supporting evidence of a prior Data Parrot result), plus the exact inputs that identify it. It also explicitly names the sibling that handles a different pagination case (get_transcript), so an agent can route correctly without opening either 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 an explicit trigger ('when the previous result offers a continuation needed to answer the question') and an explicit exclusion ('Transcript pagination uses get_transcript instead'). The precondition that a continuation must already have been returned is stated, which is the key routing fact.

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