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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: a rate limit of 60 calls per minute and a summary of the payload contents. It stops short of describing error behavior or partial/failed parses.

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 core payload description front-loaded, followed by the rate limit and endpoint. Nothing is redundant or padded.

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 carries the burden of conveying return values and does so adequately (extracted fields/tables plus document metadata), and it discloses the rate limit. Gaps remain around failure/empty-parse behavior and the distinction from the list sibling, but the essentials for correct invocation are present.

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%, so parser_id, document_id, format and include_children are all documented in the schema, including the enum semantics for format. The description adds no parameter-level detail, so the baseline of 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 (get/retrieve) and resource (parsed data of one document) and even enumerates what is returned (fields, tables, file name, page count, timestamps). It implicitly contrasts with docparser_list_document_results by scoping to 'one document', but does not name that sibling, so differentiation is inferred rather than explicit.

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: fetch results for a single already-uploaded/processed document. However, there is no explicit when-to-use guidance, no mention of prerequisites (e.g. that the document must be finished processing, cf. docparser_get_document_status), and no exclusion pointing to docparser_list_document_results for multi-document retrieval.

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