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

No annotations are provided, so the description carries the burden. It discloses that the tool returns a manifest of 90+ guides and hints at the content of those guides, but it doesn't describe the return format, whether it's a list, pagination, or any side effects. For a read-only manifest retrieval, this is adequate but not rich.

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?

A single, information-dense sentence that front-loads the verb and resource, then adds relevant detail about the content. No wasted words.

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 zero-parameter, read-only manifest retrieval, the description is largely complete. It could mention the return format or whether the manifest is a list of titles, but given the simplicity of the tool and no output schema, the description provides enough for an agent to call it 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?

The tool has zero parameters, so the schema is trivially complete. The description adds context about what the manifest contains, which is useful for an agent deciding whether to call this tool. Baseline 4 for zero params is appropriate.

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 tool's purpose: retrieving NMLP's pillar guide manifest, with a specific resource (90+ Southwest author and collectible-book reference guides) and details on content (first-edition identification, points of issue, provenance). It distinguishes itself from sibling tools by focusing on the manifest of guides rather than individual lookups or searches.

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 implies this is the tool to use when you need the overall manifest of pillar guides, as opposed to specific lookups like nmlp_identify_first_edition or nmlp_search_titles. It doesn't explicitly state when not to use it or name alternatives, but the context of sibling tools and the clear resource scope provide adequate guidance.

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