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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering safety and idempotency. The description adds valuable behavioral context by disclosing the premium cost ($0.25 USDC via x402) and payment method, which an agent needs to know before invocation. No contradiction with annotations.

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 two sentences: the first is a concise statement of functionality with concrete examples, the second adds cost and payment info. Both are front-loaded and carry value; there is no filler or redundancy.

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?

The tool has only one parameter with full schema coverage, and the description lists the types of signals returned, giving the agent a clear expectation of the output content. It also covers cost and payment. Without an output schema, this is reasonably complete for a simple lookup tool, though it doesn't specify response structure or potential errors.

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?

The schema provides 100% coverage with a clear parameter description ('Target company name to surface buying signals for') and an example. The description adds no additional parameter semantics beyond what the schema already conveys, so the baseline 3 is 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?

The description clearly states the verb ('Identify') and resource ('recent buying signals for a target company') and lists specific signal types (funding, leadership changes, expansions, hiring) and its use case (sales targeting). It does not explicitly contrast with siblings but the focus on buying intent is distinct from similar tools like 'interzoid_business_info' or 'interzoid_recent_news', though it could be clearer in differentiating.

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 implies usage via 'useful for sales targeting' but does not provide explicit when-to-use guidance, alternatives, or exclusions. Siblings like 'interzoid_private_company_deal_intel' or 'interzoid_competitor_analysis' might overlap, but no comparison is given, leaving the agent to infer selection criteria.

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