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

Annotations already establish that this is a safe, read-only, idempotent operation, so the description's main added value is noting that the result includes the draft, missing fields, and the signed filing. It does not discuss authentication sensitivity, token secrecy, rate limits, or response structure, but it does add some return-context beyond the annotations.

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?

It is a single short sentence with no wasted words, but it is a sentence fragment that is front-loaded with unclear return-content hints rather than the tool's primary purpose. It is concise but cryptic rather than efficiently structured.

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 simple read-only tool with two fully documented parameters and complete safety annotations, the essentials are covered elsewhere. However, the description does not clearly state the retrieval purpose or when to choose it over related tools, and without an output schema it should more explicitly frame what the agent will receive.

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 both the id and token parameters are already fully documented in the input schema. The description adds no parameter-level meaning, which is acceptable given the complete schema but does not exceed the baseline.

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 hints at what the tool returns ('a draft, what's still missing, and the filing') but never states a clear verb or resource, so it does not clearly say 'retrieve an application.' It is vague rather than tautological, but an agent must infer the action from the tool name and title.

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?

There is no guidance on when to use this tool versus siblings like get_filing or get_formation, nor any stated prerequisites or exclusions. The description only describes expected content, leaving usage entirely implicit.

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