Look Up State Business Registration Portal by State

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

With no annotations, the description carries the full burden. It discloses that the data is a static reference, notes which states are verified (10 Midwest) and which need sanity-checking (40 others), and mentions bulk-download availability. This provides good transparency about data quality and limitations.

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 three sentences with key information front-loaded. It is efficient and contains no filler, though one could argue the bulk-download mention could be integrated more tightly. Still very concise.

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?

Given the tool's complexity (static reference for 50 states with varying verification), the description covers the return values, use cases, data caveats, and sibling tool pointer. It is complete enough for an agent to understand scope and limitations.

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 coverage is 100% and already describes the stateCode parameter (USPS code, length, case-insensitivity). The description adds no additional semantic value beyond what the schema provides, so baseline 3 is 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 clearly states the tool's purpose: it returns the URL and agency for a US state's business-entity search portal. It uses specific verbs and resources, and distinguishes itself from the sibling tool 'business_entity_search' by noting the latter is for programmatic lookups.

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?

Explicitly provides when to use (manual verification, records requests, state search forms) and when not to use (prefer programmatic lookups via OpenCorporates). Also mentions bulk-download availability for specific contexts.

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