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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description goes beyond them by disclosing the lifecycle rule for announced_edition (present before the effective date, absent after or when nothing is announced), the data source (uscis.gov page or dated web.archive.org capture), and the absence of auth and legal-advice status. It does not discuss freshness limits or failure modes when a form is unknown.

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 response payload is front-loaded in the first sentence, followed by the announced_edition caveat and then sourcing/auth boilerplate. Every sentence carries information, though the announced_edition clause is dense enough that a reader must parse it twice; trimming would be possible but nothing is truly 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?

With an output schema present, the description does not need to enumerate return fields, yet it still explains the trickiest one (announced_edition) and names the authoritative source. Combined with the readOnly annotations, an agent has enough to call this correctly; the only gap is not stating what happens when the form number is unrecognized.

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?

There is a single parameter with 100% schema description coverage, including an I-765 example, so the schema already carries the semantics. The description adds no format, casing, or validity guidance for the form identifier, making the baseline 3 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 precisely what is retrieved: the USCIS-accepted edition of a given form plus its accepted-from and rejected-from dates, and explains the announced_edition variant. That is a specific resource and a well-scoped payload, but it never names or contrasts itself with related siblings such as list_form_changes, leaving sibling differentiation 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?

Usage is implied rather than stated: an agent can infer this is the tool for 'which edition of form X is valid now,' but there is no explicit when-to-use, no exclusion, and no routing to list_form_changes or other form-related siblings. The 'Free, no sign-in required' note is a practical prerequisite but not usage guidance.

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