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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds material context beyond them: the tool is stateless (dossier must be echoed back), it never recommends, ranks or names a robot, computes no cost, and requires no key or account. It does not describe what happens on malformed or partial dossiers, which is the remaining behavioral gap for a stateless loop.

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?

Dense but well ordered: purpose first, then the protocol constraint, then the action variant, then scope limits. Every clause carries information, though the single-block formatting makes the call protocol slightly harder to scan than a broken-out sequence would.

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?

For a stateless conversational tool with no output schema and no parameter descriptions, the return contract matters a great deal, and the description only says the sheet comes back for action='sheet'. It does not say what a normal turn returns (the next question, updated dossier) or how to recognize completion. The lang parameter is also entirely unaddressed, leaving a meaningful hole.

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 0%, so the description carries the full burden. It explains dossier (echo the previous return), answer (the reply to the question asked) and action='sheet', covering three of four parameters. lang is never mentioned, and the expected shape of the answer object is left unspecified.

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 pair: guides a buyer one question at a time through the G.R.O.U.N.D. method to a needs sheet for a first humanoid robot pilot. The stated scope (structured need, market-proven counts across the panel, triggered vigilance points, no robot named) makes the deliverable concrete. It does not explicitly distinguish itself from the close-sounding sibling build_pilot_decision_file, which an agent has to disambiguate unaided.

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 clear operational context: call with no dossier to start, then send back the previous dossier plus the answer to the question asked, and use action='sheet' to retrieve the sheet built so far. This is genuine when-and-how guidance for a multi-turn protocol. It stops short of naming alternatives or exclusions, so it falls below the top of the scale.

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