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

With readOnlyHint=true and openWorldHint=false already covering the safety profile, the description adds real context: data is 'simulated', results are ordered 'best first', and the payload is win rate plus sample size. It stops short of noting limits such as no data for untracked tickers or minimum sample thresholds.

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 dense sentence with no filler, and the key identity ('one stock across tracked influencers') is front-loaded. The trailing 'for a mode and period' feels appended rather than integrated, which slightly weakens the structure.

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?

No output schema exists, and the description does cover the return contents (win rate, sample size, ordering), which is helpful. However, with 0% param coverage and an unexplained mode enum, an agent still lacks enough to select mode/period confidently – the minimum-viable bar, not more.

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 0%, so the description carries full burden, yet it only echoes param names ('for a mode and period') without explaining what the WLO/LO/LS mode values or the period options mean. Ticker semantics are obvious, but the two enum parameters remain opaque to the agent.

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: per-influencer simulated win rate and sample size for one ticker. An agent can tell it is a per-stock, per-influencer stat lookup. It does not explicitly distinguish itself from close siblings like stock_opinions or rank_influencers, so sibling differentiation is left to inference.

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 by scope ('one stock across the tracked influencers') – an agent must infer this is the tool for comparing influencer performance on a single ticker. There is no explicit when-to-use, when-not, or alternative named (e.g. rank_influencers, stock_opinions).

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