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

Goes well beyond the annotations by disclosing the paid nature of the call ($0.01 USD default via x402), that the payment challenge carries the live price, a ten-minute cache, and a free sample path — critical context that explains why readOnlyHint is false. It stops short of saying whether failed or empty responses are still billed, or any rate limit.

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?

Three dense sentences, front-loaded with what is returned before filters, cost, and the sample pointer. Almost nothing is wasted, though the trailing sample URL is slightly tacked on rather than integrated into the payment sentence.

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?

An output schema exists, so return values need not be explained, and the description still covers filters, caching, and the payment flow. It is nearly complete for a paid read endpoint; only failure/empty-result charging behavior and sibling routing are missing.

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 100%, so both parameters are already fully documented with patterns and omit-behavior in the schema. The description only restates 'Optional tickers and since filters' without adding syntax or edge-case meaning, so the baseline of 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?

States a specific verb and resource ('Return the latest final portfolio decision per ticker as structured JSON') and enumerates the payload fields (report dates, models, source URLs, summaries). It is clear what the tool does, but it never names or contrasts the closest sibling, get_research_decisions, so the agent must infer the distinction between 'signals' and 'decisions' itself.

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?

Usage is only implied: the optional tickers/since filters and the free sample endpoint hint at how to explore or scope calls, but there is no explicit 'use this when…' or 'prefer X instead'. With siblings like get_research_decisions and read_research_report present, the absence of routing guidance leaves a real gap.

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