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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that – no information about what the tool returns, whether the region changes available content, or what the "hub" actually contains. No contradiction with annotations, but zero added value.

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?

Three words is concise but the opposite of informative – this is under-specification rather than efficiency. There is no front-loaded statement of action or scope because there is no substantive content at all.

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 no output schema, the description is the only place an agent could learn what forms are produced, in what format, or how region affects output, and it provides none of that. For a hub-style tool with a selector parameter, this leaves the agent unable to predict the response.

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 0% and the description never mentions the single `region` parameter. The enum values (US, IN, UK, other) are somewhat self-explanatory, but the description offers no explanation of what region selects or how it changes results, so it fails to compensate for the coverage gap.

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?

"Government forms hub" essentially restates the tool name (business_government_forms) as a label rather than stating what the tool does. There is no verb and no indication of what action the agent is performing, so an agent cannot tell from the description what this produces versus a document-drafting sibling like business_nda_draft.

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 when-to-use guidance, no exclusions, and no reference to any alternative among the 25 sibling tools. The agent is left to guess entirely from the name whether this lists forms, generates them, or fetches templates.

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