enrich_businesses_firmographics

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

No annotations are provided, so the description bears full responsibility. While it details the output fields, it does not disclose whether the operation is read-only, any authentication requirements, or potential side effects. The lack of any behavioral warnings leaves gaps.

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 concise, using a bullet list for output details and a short exclusion note. It is well-structured, though the list could be slightly more compact. No wasted words.

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 has one parameter and no output schema, the description is fairly complete, listing all returned fields. However, it omits details like pagination, maximum response size, or any rate limits, which could impact agent decision-making.

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 single parameter 'business_ids' has 100% schema coverage with a description that clarifies the IDs come from match_businesses, adding meaningful context beyond the schema. This helps agents understand the data source.

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 'Get firmographics data in bulk' and lists all returned fields, making the tool's purpose unambiguous. It is distinct from sibling tools like enrich_businesses_financial_metrics or enrich_prospects_profiles.

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 explicitly states when NOT to use the tool (for finding employees or leadership info), providing clear exclusion criteria. However, it does not suggest alternative tools for those cases, which would improve guidelines.

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