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

With no annotations, the description carries the full burden and does well: it discloses the $0.25 USDC price, that an unpaid call returns an x402 PaymentRequired result and does NOT execute, and that payment is verified and settled before execution. That is exactly the pre-invocation behavior an agent needs. It omits latency, rate limits, and any auth requirements beyond payment.

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?

Front-loaded with purpose, then scope, then the payment mechanics in three tight sentences with no filler. Slightly dense on the payment sequence, but every sentence earns its place.

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?

There is no output schema, but the description compensates by enumerating the returned sections (profile, offerings, market signals, developments, risks, citations, confidence, diagnostics) and explaining the payment-gated failure mode. An agent has enough to call this correctly and interpret the result.

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 both parameters are already documented in the schema. The description adds no syntax, format, or constraint detail about 'website' or 'focus' beyond what the schema provides, so the 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?

The first sentence states a specific verb and resource: 'Create a source-linked company intelligence report from a public company website,' and the second enumerates the report's contents. It is clear what the tool produces, though it never distinguishes itself from the sibling cited_research_brief, which sounds adjacent in function.

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?

Explicit intended contexts are listed (agent workflows, vendor review, sales research, partnership screening) plus one exclusion ('not for high-stakes automated decisions'), which is genuine when/when-not guidance. It stops short of naming an alternative tool for the excluded case or for overlapping research needs.

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