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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description still adds genuinely useful operational detail: a documented rate limit of 30 calls per minute, a 100-document page ceiling, and the pagination contract (next_offset is null on the last page).

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 dense sentences: what is returned and the default mode first, then pagination, then the rate limit and endpoint. Every sentence carries information an agent needs, with no filler.

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 read-only list endpoint with full schema coverage and no output schema, the description supplies the things the structured fields cannot: pagination termination (next_offset null), the rate limit, and the underlying HTTP route. An agent can call and page through this tool correctly using the description plus schema alone.

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 10 documented parameters and 4 enums, so the schema carries the parameter burden. The description restates only the page-size and offset mechanics ('up to 100 documents per call; page with offset'), adding little that the schema does not already say, so baseline 3 applies.

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 states a specific verb and resource ('Parsed data of several documents of one parser') and names the selection modes (last uploaded vs. uploaded/processed after a date). It is clear, though it never names its nearest sibling (e.g. docparser_get_document_results for a single document), so the differentiation is implied by 'several documents' rather than stated.

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?

It explains the default mode ('the last uploaded ones (default)') and the condition that enables the alternatives ('those uploaded/processed after a date'), which is enough to choose the right listing mode. It offers no explicit when-not guidance or sibling comparison, so it stops short of a 5.

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