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

No annotations are provided, so the description carries the full burden. It clearly signals a read operation via "Read" and discloses what the caller gets back: contract details, steps, Agree seal, assignee, and instructions. It stops short of explicitly saying there are no side effects, but the read-only intent is strongly conveyed.

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 compact and information-dense, with the key action and routing front-loaded. There is minor redundancy between "Use before agree_playbook / run_playbook" and the trailing "Routing" sentence, but it overall earns its place.

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 compensates by listing the meaningful fields of the returned Playbook and by clarifying the relationship to list_playbooks. It gives an agent enough context to decide when to call this tool and what to expect from it.

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 companyId, tactic_id, and tactic_title. The description adds only the concept of selecting by id or title, which is already implied by the schema's "use this or tactic_title" notes. No substantial parameter meaning is added 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 names a specific verb and resource: "Read ONE Playbook by id or title." It also enumerates the returned content (contract, steps, Agree seal, assignee, how-to) and distinguishes itself from list_playbooks, agree_playbook, and run_playbook.

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 explicitly says to use this before agree_playbook/run_playbook and points to list_playbooks as the index. It closes with an explicit routing instruction: "Inspect one Playbook ... → use this." This is clear when-to-use guidance.

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