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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds useful behavioral context: the tool returns metadata and a temporary download link that is only available once the PDF is ready.

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?

The definition is two sentences and front-loads the key behavior: metadata retrieval plus temporary link availability. The endpoint reference is compact and no sentence is wasted.

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 two-parameter read-only retrieval with full schema coverage and no output schema, the description gives the essential return context: export metadata and the temporary download link once ready. It leaves some gaps around response fields and not-ready behavior, but the core call semantics are complete.

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 schema already documents both form_id and export_id as GUIDs with patterns. The description does not add parameter syntax or usage detail beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific verb and resource: get metadata of a PDF export, including the temporary download link when ready. It distinguishes metadata retrieval from the actual export creation implied by sibling goformz_export_form_pdf, though it does not explicitly name that sibling.

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?

The phrase 'once the PDF is ready' implies this is used to check export status or retrieve the download link after an export has been initiated. However, it does not explicitly say when to use this versus goformz_export_form_pdf or goformz_get_file, nor does it state what to do if the export is not ready.

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