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

With no annotations, the description carries the full burden and does disclose a critical behavioral trait: the endpoint is now x402-paid at $0.03 per call on Base. That pricing/payment disclosure is genuinely useful. However it omits authentication requirements, return format, and any rate/limit behavior.

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 leading 'Company research $0.03' is well front-loaded, but the second sentence is historical trivia about the path's past and the bracketed payment metadata is dense machine-oriented noise. Mixed signal-to-noise.

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?

With no output schema and no annotations, the description must do all the work, yet it never says what the returned research contains or how it is shaped. The 'free'/'paid' naming conflict also risks misleading an agent about cost.

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 50%: 'q' is documented in the schema and echoed by the '?q=stripe.com' example, but the 'domain' parameter is undocumented in both schema and description. The description adds no meaning beyond the schema's existing example.

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 states the resource ('Company research') and equates it to /api/x402/company-research, so an agent can infer the output. However, the tool name says 'free' while the text says '$0.03', and the historical note ('used to return a free sample') muddies what the tool actually is today.

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 discloses that this path now costs the same as /api/x402/company-research, which implies an alternative exists, but it never says when to choose this over that sibling or over lion_company_research. No when-to-use or when-not guidance is given.

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