list_documents

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

With no annotations, the description must fully disclose behavior. It only states 'List all indexed documents'—no mention of pagination, ordering, performance implications, or how parameters like 'limit' affect results. The agent cannot anticipate important behavioral traits.

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 extremely terse (5 words), which is under-specification rather than effective conciseness. It lacks essential details that a longer, well-structured description would provide, diminishing its utility.

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?

No output schema is provided, and the description omits return value details, error handling, or behavior for empty results. For a list tool with four parameters, this description is incomplete and leaves the agent with insufficient information to use the tool reliably.

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 only 25% (only 'projectPath' has a description). The tool description adds no explanation for 'limit', 'language', or 'extension'. Given low coverage, the description should compensate but fails to clarify parameter meaning or constraints.

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' and identifies the resource 'indexed documents', making the basic purpose clear. However, it does not differentiate from sibling tools like 'search' or 'explore', and the phrase 'all' contradicts the filtering parameters available, slightly reducing clarity.

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 provided on when to use this tool versus alternatives. Siblings like 'search' or 'get_related' likely serve different querying needs, but the description offers no context for selection, leaving the agent without decision support.

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