list_documents

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

No annotations are provided, so the description must fully disclose behavioral traits. It only says 'list documents', which implies a read operation, but fails to mention pagination, keyword filtering, or any side effects. The minimal description leaves significant behavioral ambiguity for a tool with multiple parameters.

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 concise at four words and front-loaded. However, it sacrifices clarity and completeness for brevity. While no words are wasted, it omits essential details that could be added without losing conciseness.

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 the tool has 4 parameters, no output schema, and no annotations, the description is severely incomplete. It provides no information about required parameters, pagination, filtering behavior, or return format. A minimally complete description should address these aspects.

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 0%, meaning no parameter descriptions exist in the schema. The description 'List documents in dataset' does not explain any of the four parameters (dataset_id, page, limit, keyword), leaving their semantics entirely to inference from names. This is insufficient.

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 'List documents in dataset' clearly indicates the tool's action (list) and resource (documents, dataset). It distinguishes from siblings like 'get_document' (single document) and 'search_dataset' (search across datasets). However, it could be more specific about scope (e.g., pagination, filtering) to achieve a 5.

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 like 'search_dataset' or 'get_document'. There is no mention of prerequisites, such as requiring a valid dataset_id, or any exclusions. The description lacks contextual cues for appropriate usage.

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