itin_state_info

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful detail about the returned content (taxes, rate, law, URL) without contradicting the safety profile. It does not mention handling of missing states, but openWorldHint partially covers that.

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 description is a single sentence that is front-loaded with the core purpose and lists specific data points. There is no redundant phrasing or filler, making it highly efficient.

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 simple lookup tool with one parameter and no output schema, the description enumerates the return fields (taxes, rate, law, URL), which is sufficient for an agent to understand what to expect. It does not describe edge cases like unsupported states, but the simplicity and openWorldHint mitigate the gap.

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?

The schema has one required parameter 'state' with no description (0% coverage). The description's mention of 'State-level' and 'state guide URL' implies the parameter is a US state, but it does not explicitly define format, examples, or allowed values. This partially compensates for the lack of schema documentation.

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 clearly states the tool provides state-level context for ITIN holders, listing specific data fields (taxes, rate, driver's license law, guide URL). This is a distinct resource that differentiates from sibling tools like get_guide or find_itin_lenders, making it easy for an agent to select.

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 description implies usage by its specificity—when an agent needs state-specific ITIN facts, this tool is the obvious choice. It does not explicitly mention alternatives or exclusions, but the context is clear enough that no conflicts with siblings arise.

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