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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely useful behavior beyond them: results are metadata only, not document bodies, and it enumerates the metadata fields returned. It does not mention pagination behavior or auth/permission requirements, but those are partly covered by the schema's page_token/offset params.

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?

Two compact sentences, with the resource and the metadata-only caveat front-loaded before the scoping options. The trailing 'Clio: GET /documents.json' is minor traceability that doesn't help an agent act, but it costs little.

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 12-parameter, all-optional list tool with a fully documented schema and no output schema, the description covers what the tool does, how it can be scoped, and what kind of data comes back. Sorting, paging and enum semantics are left entirely to the schema, which is rich enough to carry them.

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 100% and every one of the 12 parameters is documented in the schema, so baseline 3 applies. The description only echoes the schema's framing — name search and matter/contact/folder scoping — without adding format, interaction (e.g. scope only applies with parent_id) or precedence guidance beyond it.

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?

States a specific verb and resource ('List documents') plus the exact scoping axes (matter, contact, folder, or name search) and the output shape ('metadata only: name, file name, type, size, category, dates'). An agent knows precisely what this returns and what it does not (no file contents), with no sibling document tool to confuse it with.

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 makes clear the contexts in which the tool applies — listing documents attached to a matter, a contact, a folder, or searching by name — which maps directly onto the matter_id/contact_id/parent_id/query parameters. It offers no exclusions or guidance about when a different tool would be preferable, but there is no competing document tool among the siblings, so the practical gap is small.

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