business.sos-search

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

No annotations exist; description only mentions normalization across states but omits behavioral traits like rate limits, authentication, or error handling. Lacks disclosure of any constraints.

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?

Two sentences (40 words) front-load all key information: purpose, scope, search mode, and output fields. No redundancy.

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?

Lists return fields but does not specify search behavior (e.g., case sensitivity, maximum results beyond schema limit), pagination, or empty result handling. Adequate for a simple tool but with gaps.

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?

While schema covers 40%, description clarifies that 'name' is partial match and 'entityId' is exact, and adds context about return fields and state coverage, enriching parameter understanding.

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?

Describes a specific verb-resource combination ('business registry search') with scope ('NY, CO'), search methods ('by name or entityId'), and return fields. Clearly distinguishes from siblings like business.entity-screen.

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?

Implies usage for Secretary of State business searches but does not explicitly state when to use this tool vs alternatives, nor provides exclusions or prerequisites.

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