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

Annotations already declare readOnlyHint=true, and the description adds genuinely useful context beyond that: the sort order, the pagination nature, the fact that only metadata (not rendered files) persists, and the underlying GET /docs.json endpoint. It does not cover rate limits or default page size behavior, so not a 5.

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?

Three sentences, front-loaded with the core purpose, and each adds something (scope, non-retention caveat, endpoint). The API endpoint mention is mildly redundant but not wasteful. No padding.

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?

With no output schema, the description correctly describes the return contents (name, type, test flag, creation time) and ordering, which an agent needs. Pagination defaults are left to the schema, and there is no note on total counts or paging termination, so a small gap remains.

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%, with both page and per_page documented including defaults and max, so the schema carries the parameter burden and the baseline is 3. The description only alludes to pagination generically and adds no format or constraint detail beyond the schema.

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 metadata for documents created on this account') plus the ordering scope (most recent first, paginated), so the agent knows exactly what it returns. It does not, however, distinguish itself from siblings like docraptor_get_document_status or docraptor_create_document, so it stops short of 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?

Usage is implied — enumerate documents on the account — and the caveat that rendered files are not retained tells the agent what this tool cannot be used for. But no alternative sibling is named and no explicit 'use this when...' condition is given, so this is minimum-viable routing guidance.

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