Describe a stored result

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds real behavioral context about what the response contains: typed columns with units, null/min/max stats, first/last row previews, provenance, pagination, and three ready-made queries — meaningful disclosure given there is no output schema.

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?

A single front-loaded sentence that opens with the verb and then uses a colon-list to enumerate outputs. Every clause conveys content; the list is dense but not padded. Slightly list-heavy, but no wasted sentences.

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 no output schema, the description carries the burden of describing returns and does so thoroughly (columns, units, stats, previews, provenance, pagination, suggested queries). Only minor gaps remain, such as error behavior for an invalid or expired result_id and any size limits on the preview.

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%: result_id is fully documented with a regex pattern and a concrete example ('r_8c1f0a9d3e'), and the schema itself notes it comes from this session. The description adds no additional syntax or format meaning beyond the schema, so the baseline of 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 ('Show a stored result's summary again') and enumerates exactly what the summary contains, so the agent knows this is a re-display/describe operation rather than a new query. It does not, however, explicitly contrast itself with siblings like results_query, results_sample, or results_list, so sibling differentiation is left to inference.

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?

The word 'again' hints that this re-shows a summary produced earlier (e.g. by results_query), implying usage context. But there is no explicit when-to-use versus results_list/results_query/results_sample, and no stated preconditions such as the result_id having to originate from this session's prior query.

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