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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered and the bar is lower. The description adds genuinely useful behavior not in annotations: a $0.25 USDC x402 charge per call, which affects whether an agent should invoke it speculatively. It says nothing about failure modes for unrecognized or ambiguous companies, or about latency/coverage limits.

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 dense sentences plus a short cost clause, with the payload contents front-loaded and the use cases and price trailing. Every clause carries information; nothing is restated from the name or schema.

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?

For a two-parameter, no-output-schema tool, the description compensates well by enumerating return contents and disclosing the per-call cost. It is slightly incomplete on input robustness — nothing tells the agent whether the company name must be exact, whether private companies are covered, or what an empty result means.

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% and both params are fully documented in the schema, including the language enum, so the baseline of 3 applies. The description mentions only the target company implicitly and adds no syntax, format, or ambiguity-resolution guidance beyond the schema.

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 names the resource concretely and enumerates the signal categories returned (leadership changes, funding, hiring, expansion, tech changes, budget indicators, pain points) plus derived outputs like signal strength score and decision makers, so an agent knows exactly what it gets back. It stops short of explicitly routing away from overlapping siblings such as interzoid_recent_news or interzoid_tech_stack, so the differentiation is inferable rather than stated.

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?

It gives clear usage context — sales prospecting, account-based marketing, lead prioritization — which tells the agent what task class this tool serves. There are no explicit exclusions or named alternatives, so an agent deciding between this and the news or tech-stack tools gets no direct guidance.

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