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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world). The description adds genuinely non-obvious behavior: the store is in-process with a TTL and returns 404 once expired, plus that the call is free. That expiry/404 detail is exactly the kind of operational fact an agent needs and cannot infer from structured fields.

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 clauses, front-loaded with the action and resource, then cost, then failure mode. No sentence is filler.

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?

With only one required parameter, a full output schema, and annotations carrying the safety profile, the description covers everything needed to invoke correctly, including the expiry failure mode. Minor gap: it doesn't indicate payload size limits or what a truncated payload's shape looks like, though the output schema likely handles that.

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 100% and the schema already documents dataRefId as a UUID from the summarized response's dataRefId field. The description's mention of 'from a summarized or dataRef response' restates that origin rather than adding new syntax or constraints, so 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 (Fetch) and a precise resource (full truncated tool/workflow payload by dataRefId), plus the triggering context (a summarized or dataRef response). An agent can immediately tell this apart from siblings like get_tool_schema or get_run, which serve different purposes.

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?

Clearly names the condition that selects this tool: when a prior response was summarized and exposed a dataRefId. It does not name an explicit alternative or exclusion, but the trigger condition is unambiguous.

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