list_documentation

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

With no annotations, the description carries the full burden for behavioral disclosure. It implies a read-only operation ('list') but does not explicitly state safety or output behavior. The claim of 'all' conflicts with the schema's filter parameters, creating ambiguity about whether results are unfiltered or filterable.

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, short sentence with no redundant words. It is appropriately concise for a simple listing operation, though it sacrifices detail.

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 description omits the optional filtering capability exposed in the schema and does not differentiate from search_documentation. With no output schema and no annotations, the description should clarify what is listed and how filters relate, but it does not.

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 input schema already provides 100% coverage with descriptions for both optional parameters (tag and category). The tool description adds no additional parameter semantics, so it meets the baseline without enriching the schema.

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 'list' with the resource 'documentation sources' and includes scope ('all available'). It is clear and unambiguous, but it does not explicitly distinguish from sibling tools like search_documentation, which likely targets specific items.

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?

No guidance is given on when to use this tool instead of search_documentation or the add/update tools. The description does not mention scenarios, exclusions, or alternatives, leaving the agent without context for tool selection.

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