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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds genuine context beyond that: the response carries validation issues and still-unanswered questions, and the revision number is a required input for update_application and generate_filled_pdf — a real cross-tool constraint not visible in the schema.

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 sentences, zero filler. The payload contents are front-loaded and the usage clause follows, so an agent gets the what before the when.

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?

No output schema exists, but the description compensates by enumerating the returned fields (answers, revision number, validation issues, unanswered questions). Combined with annotations covering the safety profile and a fully documented single parameter, nothing needed to call this correctly is missing.

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% and the single application_id parameter is already documented as a UUID returned by create_application. The description adds no syntax or format detail beyond the schema, 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?

States a specific verb (read) and resource (saved draft/application), then enumerates exactly what comes back: current answers, revision number, validation issues, and unanswered applicable questions. This is clearly distinguishable from create_application, update_application, and validate_application.

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?

Gives two concrete use cases: resume a draft, or display all answers before confirming generation. It also names the downstream consumers of the returned revision number (update_application, generate_filled_pdf), which routes the agent effectively. No explicit 'when not to use' or named alternative read path, so not a 5.

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