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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds two traits annotations cannot express: the read is of a saved snapshot (point-in-time semantics) and the error-model caveat 'A failed lookup is not an empty application,' which prevents an agent from misreading a failure as an empty record.

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 with the purpose front-loaded and no filler; each sentence contributes either scope, timing, or error semantics. Minor cost: 'Forms' is capitalized as an external concept the description never defines, assumed to be obvious from the product context.

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?

An output schema exists, so return values need not be described. Given a single required ID, the description covers purpose, timing, snapshot semantics, and failure interpretation. What remains thin is the relationship to list_applications and where the taskId originates.

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% and the single parameter taskId carries only a UUID pattern. The description never mentions taskId, where it comes from, or whether it is the application/task identifier returned by list_applications. The param name is fairly self-evident, which keeps this above 1, but the description does not compensate for the coverage gap.

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?

A specific verb-plus-resource: 'Read the saved safe snapshot of your application.' The 'saved safe snapshot' phrasing signals this returns a persisted, validated state rather than live data. It does not explicitly distinguish itself from the sibling list_applications, so an agent must infer that one is single-record and one is enumerating.

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?

Names two concrete trigger points: 'Re-read after returning from Forms or before preparing submission.' That is real, actionable timing guidance tied to sibling workflows (open_application_form, prepare_application_submission). It stops short of an explicit 'use X instead when...' exclusion against list_applications or update_application.

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