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

Annotations already cover read-only/idempotent safety, and the description adds substantial context beyond them: required scopes (applications:read, documents:read), a five-minute link expiry that also triggers on disconnect or permission change, presence of candidate data, and no credit charge. That is exactly the extra behavior an agent needs.

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 short sentences, front-loaded with what is returned, followed by prerequisites and operational caveats. No filler or repetition.

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 payload (validated PDFs and extracted text/manifest), and it covers auth scopes, link lifetime, and cost. Nothing material for correct invocation is missing for a single-parameter read tool.

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% for the single integer application_id, so the description carries the burden, but it adds no meaning about the parameter's format or source. The parameter is self-evident by name, so this is not a severe gap, but nothing beyond the schema is contributed.

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 (Retrieve) and a precise resource (validated PDFs plus extracted text/manifest) scoped to an application package. Unlike siblings such as get_candidate_context or prepare_application, it is clear this returns the assembled document bundle rather than context or a mutation.

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 by the name and the required application_id, but the description never states when to call this versus get_candidate_context or prepare_application, nor any preconditions beyond the required scopes. It gives operational constraints (expiry, credit cost) but no routing guidance between alternatives.

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