lookup_business

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

No annotations provided, so description carries full burden. It discloses that the tool queries SEC EDGAR, explains match/no-match outcomes, and notes escalation condition. Does not explicitly state read-only nature or discuss rate limits/authentication.

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 plus a note, front-loaded with purpose. Every sentence earns its place with no wasted text. Compact and 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?

Tool has no output schema, so description should explain return values. It implies a match result but does not explicitly describe the output format or fields. Missing this key detail for a simple lookup tool.

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 has 100% coverage with descriptions for both parameters. Description adds no new semantics beyond the schema; both params are adequately documented. Baseline 3 as schema already covers meaning.

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 it looks up a business in the SEC EDGAR registry to verify registration. It uses specific verb+resource (look up, SEC EDGAR registry) and distinguishes from sibling tools (risk assessment, screening, identity verification) by focusing on SEC registration.

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 says 'Call for any business applicant' and provides important interpretation guidance (no-match expected for LLCs, red flag for claimed public companies). Lacks explicit exclusions or alternative tool references for similar lookups.

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