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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, but the description goes further by stating 'Read-only. Creates no purchase, checkout, or payment obligation.' This adds domain-specific business guarantees (no financial commitment) that are not captured in the annotations, providing unique behavioral context an agent needs to know.

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 front-loaded: the first sentence states the core purpose, followed by two brief clarifications. Every sentence earns its place with no redundancy or fluff. It is appropriately sized for a zero-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?

Given there is no output schema, the description adequately specifies what the tool returns (list of playbooks and their problem areas). It also conveys the read-only nature and lack of obligations. No additional information is needed for an agent to call this tool correctly; it is fully specified for its simple scope.

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?

The tool has zero parameters, so schema coverage is vacuously 100%. Per the baseline rule for 0 parameters, the score is 4. The description does not need to explain parameters, and it correctly focuses on the output (listing playbooks and problem areas) rather than inputs.

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 action (list), the resource (public Systemia Field Library playbooks), and the output scope (their problem areas). This distinguishes it from siblings like get_field_playbook (fetch a specific playbook) and match_contractor_problem (match problems to contractors). The verb 'list' vs 'get' and 'match' makes the purpose unambiguous.

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 begins with 'Use this to list...', providing a direct usage instruction. However, it does not explicitly mention alternatives or when not to use it, such as pointing to get_field_playbook for retrieving a single playbook. The sibling names are informative, but the description itself lacks explicit routing, so it falls short of a 5.

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