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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds valuable behavioral context: it states what the tool returns (workflow, stages, references, rule-kit version) and the critical privacy constraint ('never send their text to this server') and that playbook tools take only ids. This goes beyond the annotations and helps the agent understand side effects and data handling.

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 bit long but front-loaded with purpose and use cases. Each sentence serves a function: what it does, when to use, what it returns, follow instructions, privacy note, and id-only note. No redundancy; it's efficient despite length.

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 tool with one parameter and no output schema, the description is thorough. It covers the return value, instructions to follow, privacy, and parameter type. It doesn't need more detail given its simplicity, though it could mention if there are any side effects (none expected given idempotent hint). Overall, complete for its purpose.

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 coverage is 100%, so the schema already documents the id parameter with allowed values. The description adds meaning by clarifying that the id is a playbook identifier, not content, and reinforces that the user's text should never be sent. This helps the agent correctly construct the parameter and avoid misuse, adding value beyond the schema.

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 the verb ('start') and resource ('guided compliance playbook'), and it explicitly names the use cases (FNMA AI lender letter, FHA/VA/USDA loan QC) that distinguish it from sibling tools like get_playbook_reference or list_playbooks. The purpose is unambiguous and specific.

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 description gives explicit when-to-use conditions ('use this when the user asks to run...') and instructs to follow the returned instructions exactly. It does not explicitly list when not to use it, but the named scenarios and the note that playbook tools take only ids provide clear context. It could be improved by contrasting with get_playbook_kit or list_playbooks, but it's still strong.

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