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

Adds substantial context beyond the annotations: missing answers surface as review questions, extra answers are treated as user reports and not persisted, output is a protected expiring PDF, and the draft neither files an application nor decides eligibility. This is consistent with readOnlyHint=true since nothing is written back to the review.

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?

Purpose is front-loaded, followed by permissions, answer handling, and limits; almost every sentence carries distinct information. The caveat list at the end is dense but each clause (no official application, no eligibility decision, no savings estimate, no filing) sets a real expectation.

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 multi-permission, nested-parameter tool with no output schema, the description covers return format (expiring PDF), permission gating, and the crucial non-effects. The remaining gap is the un-narrated role of the two required ID parameters.

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 coverage is only 25%, and the description compensates partially by explaining how the nested 'answers' object is treated (missing vs extra answers) and the conditional semantics of use_connected_va_records. However, review_id and saved_property_id are never explained in the description, leaving some parameters documented only by bare types.

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 and resource ('Create a free private veteran review PDF for the selected saved review'), clearly distinct from siblings like review_veteran_requirements or get_owner_review_details. The scope (per selected saved review) makes it selectable without opening the schema.

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 clear preconditions: owner:read required, VA connection optional, and owner:va plus explicit per-applicant user choice needed for connected facts. It does not explicitly contrast with siblings like review_veteran_requirements, so the routing guidance is contextual rather than exhaustive.

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