clio_list_documents

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to restate those. It adds the routing scope ('only through the exact project/account governed connector authority') and notes that Spring verifies the effect must be 'read', which is useful behavioral context. However, it does not disclose output behavior, pagination, or the meaning of the openWorldHint, and the approval_ref line about 'when resuming a write' is generic boilerplate that could confuse for a read-only tool.

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 structure is clean and the parameter list is front-loaded, but the first line redundantly restates the tool name and the effect/approval_ref lines are generic platform boilerplate that could apply to any connector operation. It is not bloated, yet it contains some filler rather than only tool-specific, purpose-relevant content.

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 output schema exists and annotations cover safety, the description does not need to explain return values or read-only semantics. But it never states what criteria or arguments cause documents to be listed, and it gives no sense of result scope or filters. The routing and effect constraints make it minimally viable, but an agent would still be guessing about the actual document-listing behavior.

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%, so the description carries the burden of explaining parameters, and it does so for all seven. Each argument gets at least a gloss, and 'effect: Required and must be read; Spring verifies it' clarifies the enforcement rule beyond the schema's const. The meaning of 'arguments' remains vague, but the description adds substantive semantics the schema lacks.

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 restates the operation name ('Clio connector operation list_documents') without explaining what the tool actually does—that it returns a list of documents or what kind of documents are listed. The only additional statement is a routing constraint, not a functional purpose. This is effectively a tautology of the tool name.

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 versus alternatives like search_documents, document_intelligence_search_documents, or clio_get_document. The 'routes only through the exact project/account governed connector authority' line is an authorization constraint, not a usage condition or alternative-selection rule.

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