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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description adds real value by disclosing the returned payload (issuing agency source, current edition, date older editions are rejected, plus a browser fill-and-sign page). With no output schema, this return-value detail is exactly the burden the description must carry. Missing only operational caveats such as coverage limits or rate/network behavior.

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?

Front-loaded with the verb and scope, and the usage sentence lands at the end. Slightly padded by the six-code example run (W-9, W-4, 1099-NEC, I-130, I-765, N-400), which conveys coverage breadth but is longer than strictly needed.

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 one-parameter lookup tool with a read-only annotation profile and no output schema, the description is nearly complete: it states scope, trigger, and return contents. An agent can call it correctly. Only the absence of any sibling routing hint keeps it short of full marks.

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 'query' parameter is already documented with examples ('W-9' or 'green card application'), so the baseline is 3. The description's form-code list reinforces the expected input format but adds no syntax or normalization rules beyond what the schema states.

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?

Specific verb ('Find') plus a precisely scoped resource: official government forms from named jurisdictions with examples (W-9, W-4, 1099-NEC, I-130, I-765, N-400). It also enumerates what the tool returns (issuing agency source, current edition, rejection date for older editions), which distinguishes it instantly from the generic sibling PDF tools like find_pdf_tool.

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?

Explicit trigger condition: 'Use this when a user asks where to get, fill in or sign a form.' That is clear when-to-use guidance, but it never names or excludes an alternative (e.g., the generic find_pdf_tool) so the agent must infer the routing choice on its own.

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