List Imported Documents

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds context about storage location ('local ThumbGate state'), which is mildly helpful but doesn't disclose other behaviors like pagination, sorting, or data freshness. No contradiction with annotations.

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 concise sentence that is front-loaded with the action and resource. Every word adds value; there is no redundancy or unnecessary information.

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?

For a simple read-only list tool with filters and no output schema, the description adequately covers what the tool does and where the documents are stored. It is complete enough for most use cases, though it could optionally mention default ordering or data latency.

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 has 100% description coverage for all three parameters (query, tag, limit), each with clear descriptions. The tool description does not add additional meaning beyond what the schema provides. Baseline 3 is appropriate as the schema already sufficiently explains the parameters.

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 'List imported policy and runbook documents', specifying the action (list) and the resource (imported policy and runbook documents). This distinguishes it from siblings like 'get_imported_document' (single document retrieval) and 'import_document' (importing new documents).

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?

The description provides clear context for when to use the tool: to list imported documents. While it doesn't explicitly exclude alternatives or provide when-not guidance, the context is sufficient for a simple list tool. Siblings like 'search_thumbgate' or 'get_imported_document' are implied as alternatives for different needs.

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