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

With no annotations supplied, the description carries the full disclosure burden and it does deliver the most decision-critical behavior: a $0.02 USDC charge via x402 on Base, settled only on successful resolution and $0.00 on a miss. That is exactly the kind of cost/side-effect context an agent needs before invoking a paid tool. It does not cover auth prerequisites beyond the payment header, rate limits, latency, or error behavior on ambiguous input.

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 price and Free-on-Miss rule are front-loaded, which is good, but the $0.02/$0.00 policy is stated three separate times across the text, making it noticeably repetitive. Every sentence is relevant, yet the same fact is re-sold rather than reinforced with new information.

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?

No output schema exists, so the description must describe return values — and it does, listing seven concrete returned fields plus the miss case. Payment mechanics are fully explained. Missing only input edge cases (both domain and name supplied, partial matches) and failure handling, which keeps it short of a 5.

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 description coverage is 100%, so the schema already documents domain, organization_name as a fallback, and the optional _x402_payment payload. The description restates the domain-first resolution path and adds nothing about input format, normalization, or how the anyOf requirement interacts with providing both fields. Baseline 3 applies.

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?

States a specific verb and resource ('Enriches full organization profile by company domain') and enumerates exactly what comes back: founded year, employee count, industry, funding history, revenue, tech stack, departmental headcount, HQ phone. It is clearly a single-organization tool, so an agent can distinguish it from enrich_person and bulk_enrich_organizations by name, but the description never explicitly names or contrasts those siblings.

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?

Usage is only implied: call it when you have a company domain (or brand name as fallback) and need firmographics. There is no explicit guidance on when to prefer bulk_enrich_organizations for multiple domains, when to call get_enrichment_quote first, or what to do when the domain is ambiguous.

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