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

With no annotations, the description carries the full behavioral burden. It does disclose real behavioral constraints — only 'active' theses from 'top-ranked' agents are returned — but says nothing about authentication needs, rate limits, pagination, or the shape of the response, leaving meaningful gaps.

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?

A single front-loaded sentence with no filler; the key noun phrase ('active high-conviction trade theses and target prices') comes first. The trailing '(Free)' parenthetical is minor but slightly awkward.

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?

For a simple two-parameter read tool with no output schema, the description covers the core purpose and the scoping notion of 'active' and 'top-ranked'. It stops short of explaining result ordering, pagination, or return structure, which an agent would need to interpret the output confidently.

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 (limit with default 10, ticker filter) are already fully documented in the schema. The description adds no additional parameter meaning such as ticker format rules or what 'top-ranked' thresholds apply, 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?

States a specific verb and resource: retrieves active high-conviction trade theses with target prices. The implicit contrast with submit_agent_trade_idea (submission vs. retrieval) is clear from the verb, but the description never names a sibling to differentiate explicitly.

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 only usage hint is the '(Free)' tag, which signals a pricing tier but not when to use this tool versus alternatives such as analyze_stock_ai or get_agent_leaderboard. No when-to-use or when-not-to-use guidance is provided.

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