enrich_organization

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

With no annotations, the description discloses cost (1 credit) and output details (company size, industry, etc.), and notes domain auto-cleaning. It lacks disclosure on rate limits or side effects, but for a read-like enrichment tool, this is satisfactory.

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, zero waste. The first sentence states purpose and cost, the second lists output. Essential information is front-loaded.

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 no output schema, the description adequately lists key returned fields. It could mention error cases or partial enrichment, but is complete for a simple enrichment 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 already describes domain with 100% coverage. The description adds value by implying the tool works on a single organization and listing returned fields, though parameter specifics are already clear.

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 uses specific verb 'enrich' and resource 'organization by domain', clearly stating the action. It distinguishes from siblings like 'enrich_person' and 'bulk_enrich_people' by specifying 'single organization'.

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 mentions credit cost, which is key usage context. However, it does not explicitly state when to use this tool versus batch alternatives or mention any prerequisites or exclusions.

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