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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond by disclosing the pricing/rate-limit model (5 free calls per day per IP, shared with the other tools, then $0.01 USDC per result via x402 on Base) and the exact conditions under which no charge occurs. This is exactly the kind of operational context annotations cannot carry.

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?

Purpose is front-loaded in the first clause, followed by outputs and then billing rules, so nothing is buried. It is dense (one long colon/semicolon-delimited paragraph) but nearly every clause carries actionable information, with only slight redundancy in the output enumeration.

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?

An output schema exists, so return values need not be explained, yet the description still enumerates the key outputs for ranking decisions. With annotations, schema, and output schema all present, the definition is complete for an agent to select and invoke this tool correctly.

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 single 'domain' parameter already has a description and example, so the schema does the heavy lifting. The description implies the domain is a public company domain but adds no format or syntax detail beyond the schema, making the baseline 3 appropriate.

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 ('turns a company domain into a hiring-based buying-intent score from its public job board') and enumerates the concrete outputs (intent_score 0-100, hiring_status, open roles, roles in last 30 days, hiring by function). This clearly differentiates it from the sibling get_company_open_jobs, which returns raw postings rather than a derived score.

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 states the usage context: 'Use to rank or prioritize accounts before outreach.' It also gives a conditional rule for when the call is not billed (no job board, no open jobs, generic name-only match). It does not name alternative siblings to use instead, so it falls short of a full 5.

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