documents-list

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

Lacking annotations, the description must disclose behavior. It only states 'List all documents' without mentioning pagination, scope (user vs. workspace), auth requirements, or response format. The absence of output schema amplifies the gap.

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?

Extremely concise (3 words) but lacks additional context that would be beneficial. It is not verbose but could be improved without adding significant length.

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?

Given no parameters, no output schema, and no annotations, the description is too sparse. It does not clarify scope, pagination, or response structure, leaving the agent with insufficient information to select or invoke 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?

With zero parameters and 100% schema coverage, the description adds no parameter info, which is acceptable. Baseline 4 applies as no parameter details are needed.

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?

Description clearly states 'List all documents,' providing a specific verb and resource that distinguishes it from sibling tools like documents-search (filtered) and documents-get-by-id (single).

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 on when to use this tool versus alternatives. For example, does not mention that filtered listings should use documents-search or that updates require documents-update.

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