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

Annotations only declare readOnlyHint/openWorldHint, but the description adds the economically critical facts: $3 USDC per call via x402, no charge when too few sources answer, and the async check-before-queue-and-charge behavior. It also discloses that the output includes a pass/meeting/strong-interest recommendation and that market claims are checked against web search. This is well beyond what structured fields convey.

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 and nothing is wasted, though the opening sentence is a long run-on inventory of memo sections. Slightly heavy but each listed section tells the agent what it will get back.

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, the description correctly carries the return-value burden by enumerating the memo contents, PDF deliverable, and recommendation. The one gap is the async flow: it says a job id is returned but never explains how the finished report is retrieved, which matters for a 7-parameter tool with a paid async mode.

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 86%, so the baseline is 3, and the description earns above that by framing pdf/url/text/file_base64 as mutually alternative input modes (the 'or' phrasing), which the schema does not state, and by explaining the async=true charging sequence. It does not clarify the bare 'company' parameter, which is undocumented in both places.

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+resource ("Investment memo from a startup pitch deck") and enumerates the deliverable sections, so an agent can distinguish it from report_company, report_market, and the other 'report_*' siblings without opening a schema. The accepted input forms (PDF, Word, URL, text) are named up front.

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 is clear when to reach for this tool: you have a startup pitch deck in one of four supported forms and want a diligence memo. It also explains the async path and the no-charge condition, which are genuine usage conditions. It stops short of naming alternatives (e.g. report_company for an already-public company rather than a deck), so it is clear context without exclusions.

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