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

Annotations already establish that this is read-only, idempotent, and non-destructive, so the description's main contribution is the return scope: 'public metadata, guide links, and landing page.' The explicit statement that 'Paid content is never returned' adds meaningful boundary information beyond the annotations.

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?

Two sentences with no filler; the action and resource are front-loaded and the additional exclusion ('Paid content is never returned') earns its place. Every sentence adds relevant context.

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 single-parameter read tool with read-only/idempotent annotations, the description covers what is returned, what is excluded, and the fact that it targets one known playbook. No output schema exists, but the description sufficiently describes the return content for an agent to decide and invoke correctly.

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%, and the description does not explain the slug parameter or how to obtain/format it. The property name 'slug' carries some meaning, but with low schema coverage the description should have compensated and did not.

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 states a specific verb ('Read') and resource ('public metadata, guide links, and landing page for one known Field Library playbook'), making the core action clear. It distinguishes itself from siblings by emphasizing 'one known' playbook rather than discovery or matching, though it does not name 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?

The phrase 'one known Field Library playbook' implies this tool is for when the caller already has a specific playbook identifier, which is reasonable guidance. However, the description does not explicitly state when to prefer this over discover_field_playbooks or match_contractor_problem, nor does it mention exclusions.

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