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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context by enumerating the document categories and explicitly framing this as the first step in a list-then-read workflow, going beyond what the annotations state.

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 front-loaded with the action and scope, then gives the output fields and the recommended next step. The longer enumeration of document categories is purposeful rather than padded because it tells the agent exactly what content will be listed, and there is no redundant or filler wording.

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 read-only list tool with one optional and fully documented parameter, the description covers scope, output composition, and usage order. The annotations carry the safety semantics and an output schema exists, so nothing an agent needs to invoke this tool correctly is missing.

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 100%, and the sole optional filter parameter is fully documented in the input schema ('documents whose id, title or section headings contain this text'). The description adds no additional parameter semantics, so the baseline score of 3 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 uses a specific verb and resource ('List every classifier.dev document') and names the exact set of documents included, making the tool's scope unmistakable. It also states the returned shape (id, title, section headings, size) and points to read_doc as the follow-up, helping distinguish it from the sibling that retrieves individual documents.

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 an explicit workflow instruction: 'Call this first, then read_doc for the one you need,' so an agent knows when list_docs is the right entry point. It does not, however, contrast list_docs with search_docs or state when search_docs would be preferable, which leaves some usage ambiguity among the sibling tools.

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