Get a metadata simulation

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), and the description adds 'instant' latency context plus a breakdown of the returned payload, which matters because no output schema exists. It stops short of describing size limits or pagination, but for a single-read tool this is solid added context.

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?

The purpose is front-loaded, but the middle clause ('This is what list_metadata_simulations cannot carry, and it is what makes a past run worth picking up: the text is here') is rhetorical filler that does not add selection or invocation value. The definition is longer than the task requires.

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 usefully enumerates the returned contents and confirms the operation is read-only and instant, which is enough for an agent to call it correctly. Minor gaps remain around payload size or field formatting, but nothing essential is missing.

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% and the schema already documents that id is the saved run id from list_metadata_simulations or simulate_metadata's saved.id. The description restates the same provenance without adding format nuances beyond the schema, so the 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 precise verb and resource ('Read one saved listing draft in full') and enumerates exactly what comes back: the four scored fields, assumed context, score, and findings. It explicitly contrasts with the sibling list_metadata_simulations, so an agent can distinguish the two 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?

It names where the id comes from — a row of list_metadata_simulations or simulate_metadata's saved.id — which is the practical prerequisite for calling it. It implies the use case (recovering the full text of a past run) but gives no explicit when-not or exclusion guidance.

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