enrich_businesses_technographics

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

With no annotations, the description must disclose all behavioral traits. It only implies a read operation ('Get ... data') and does not mention authentication, rate limits, data freshness, or potential side effects. The extensive output description does not compensate for missing behavioral context.

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 front-loaded with the purpose and then provides a structured list of return categories. While the list is long, it is directly useful for an agent to understand output content. It could be more concise but is not verbose.

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 absence of an output schema, the description thoroughly explains the return value structure with 21 categories. It covers the essential information needed to use the tool. However, it lacks context on error handling, limits, and data recency.

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 the parameter 'business_ids' has a description. However, the tool description adds no new meaning beyond the schema's description. Baseline score of 3 is appropriate as it neither improves nor degrades 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?

The description starts with 'Get technographics data in bulk,' which clearly specifies the verb 'get' and the resource 'technographics data.' The detailed list of categories distinguishes it from other enrich tools like enrich_businesses_firmographics or enrich_businesses_financial_metrics. It is specific and unambiguous.

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?

No guidance is provided on when to use this tool versus its siblings. The description does not mention prerequisites, alternatives, or scenarios where this tool is preferred. The agent must infer usage from the tool name alone.

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