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

The description calls this a 'terminal, idempotent write', but the annotations declare idempotentHint=false — a direct contradiction between the prose and the structured safety profile. The otherwise valuable context (api:respond scope, 409 = already recorded, 404 = not yours, terminal write) is undermined by this conflict.

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 front-loaded: purpose first, then id provenance, then error semantics and the trade-execution disclaimer. Every sentence adds distinct information, though the parenthetical clauses make it longer than strictly necessary.

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 non-readOnly mutation with no output schema, it covers scope requirements, id sourcing, error-code meanings, terminal behavior, and side-effect boundaries. It omits success return shape and the semantic meaning of the response enum values, but is otherwise substantial.

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 must carry the load. It explains recommendation_id well (provenance and the 'never snapshot_id' warning), but the second parameter, response, is completely unaddressed — no meaning is given for accepted/rejected/modified beyond the enum values themselves. Partial compensation only.

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 ('Record YOUR response to a pending recommendation') and explicitly delineates the boundary against the sibling execute_recommendation ('It does NOT execute a trade'). An agent can distinguish this from execute_recommendation, generate_recommendation, and list_recommendations without opening any 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?

Gives concrete guidance on where recommendation_id must come from (generate_recommendation, a ledger.status id, or a list_recommendations(status=pending) row) and an explicit exclusion ('never snapshot_id'). It stops short of naming the execute path sibling as the alternative when the user actually wants to trade, so routing is implied rather than fully spelled out.

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