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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds context about the document types and the ordering instruction, but does not disclose additional behaviors like pagination or performance characteristics. Since annotations carry the safety burden, the description's extra context is useful but not essential to behavioral transparency.

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 a single, reasonably concise sentence that front-loads the purpose and lists examples, then adds a clear usage directive. It is not overly verbose and every clause adds value, though it could be split into two sentences for readability.

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?

The tool has an output schema, so return values need no explanation. The description covers what the tool does, what it returns, and when to use it. It does not mention the filter parameter, but the schema covers that. For a listing tool with rich annotations, this is adequate and complete.

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 filter parameter is fully documented in the schema. The description does not add any parameter-specific information beyond what the schema already provides, so the baseline of 3 applies.

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 lists all classifier.dev documents, enumerates specific document types, and specifies the returned fields (id, title, section headings, size). It also explicitly contrasts with read_doc by instructing to call this first, distinguishing it from at least one sibling tool.

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?

Provides explicit usage guidance: 'Call this first, then read_doc for the one you need.' This clearly tells the agent when to use this tool relative to read_doc. It does not mention search_docs or get_examples, but the primary alternative is addressed, and the 'first' directive gives a clear starting point.

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