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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the non-mutating safety profile is known. The description adds only that the target is an existing application and that the output is a form, without saying whether the upload occurs later through a separate call or whether any IDs are validated. This is modest added context against a low bar.

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?

A single front-loaded sentence with no filler or repetition. Its brevity is clean, though it also means nothing is said about parameters or outcome.

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 tool with five undocumented parameters, no output schema, and overlapping siblings, one sentence is not enough. The agent does not know whether this returns a URL, a form schema, or a UI prompt, nor which identifier the form attaches documents to.

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?

Five parameters (id, fileName, enquiryId, documentType, applicationId) have 0% schema description coverage and the description mentions none of them. It gives no clue which of the three ID-like fields is the right one to pass, nor what documentType or fileName control. With all parameters optional the tool is technically callable, but the semantics are entirely opaque.

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: it displays a form for uploading supporting documents, scoped to an existing application. An agent can picture the action clearly. However, it never distinguishes itself from the sibling upload_offer_documents or display_offer_form, so the boundary between 'display the form' and 'actually upload' is left to inference.

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 call this versus the closely related siblings display_offer_form and upload_offer_documents, and no preconditions (e.g., an application must already exist) are spelled out beyond the passing phrase 'existing application'. The agent gets a purpose but no selection logic.

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