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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds genuinely new context: nothing is downloaded or parsed, and the transcript of a long episode is large, which is a practical payload-size warning an agent can act on.

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: the deliverable first, then the precondition, then the parameter tip. Front-loaded and largely waste-free, though 'as text you can read and pass on' is slightly padded.

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?

Covers the precondition, the no-download delivery model, and the size caveat; with no output schema, the description sensibly tells the agent what the return content is. Missing only failure-mode guidance for orders that are not yet done.

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 100%, so the schema already documents order_id, api_key, and include. The description's 'use include to fetch only what you need' reinforces intent but adds no syntax or format detail beyond the schema's comma-separated enumeration. Baseline 3 applies.

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 and resource set (show notes, transcript, edit summary) and the delivery form ('as text you can read and pass on'), which distinguishes it from the file-download siblings. An agent can tell immediately what it returns and in what shape.

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 precondition: 'Call it once barevalue_status reports "done"', which is exactly the routing signal an agent needs. It does not name an alternative for the case where the order is not yet done, but the gating condition is clear.

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