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

With no annotations available, the description carries the full burden of behavioral disclosure. It explicitly states the tool is 'read-only' and 'deterministic', which are valuable behavioral guarantees beyond what the schema conveys. It does not describe side effects or failure modes, but the read-only claim substantially covers the main behavioral concern for a plan-generation tool.

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 description is a single sentence with no filler or redundancy. It front-loads the most important traits ('deterministic', 'read-only') and the artifact produced, making it appropriately concise for a simple two-parameter tool.

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?

The tool has only two parameters and an output schema, so the description does not need to explain return values. However, the meaning of 'playbook_id' is left entirely to inference from the tool name, and 'finding' is under-explained. It is minimally viable for a basic invocation but has clear gaps around parameter semantics and selection context.

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 compensate, but it only loosely maps to the 'finding' parameter via the phrase 'for a finding'. It says nothing about the required 'playbook_id' or how the optional 'finding' value affects the output.

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?

The description clearly states a specific action ('Build') applied to a specific artifact ('phase, gate, and evidence checklist') and scopes it to 'a finding'. It distinguishes itself from obvious siblings like recipes_playbook_get and recipes_playbooks_list by emphasizing plan/checklist generation, though it does not explicitly contrast itself with those alternatives.

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?

There is no guidance about when to use this tool versus the many sibling recipe/playbook tools. The phrase 'for a finding' implies one use case, but there are no explicit conditions, prerequisites, or exclusions to help an agent choose it over alternatives.

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