opendota_hero_stats

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds only the nature of the metrics returned, with nothing about response shape, freshness of the data, or whether all brackets are returned at once — leaving the 'per bracket' phrasing unexplained.

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?

One front-loaded sentence with no filler; the resource and the payload are stated immediately.

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 no-param read tool this is close to adequate, but with no output schema the description is the only place to learn what actually comes back — e.g. whether the response is per-hero records each containing per-bracket win/pick rates, or a flat aggregate. The 'per bracket' claim without any explanation of how brackets are represented leaves a real gap.

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?

The tool takes zero parameters, so there is no parameter semantics burden and the baseline of 4 applies. The description correctly implies no required input.

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 ('Get Dota 2 hero statistics') plus the content returned ('pick/win rates per bracket'), which is meaningfully more specific than a bare name restatement. It does not, however, distinguish itself from the sibling 'opendota_heroes', so an agent must infer that this returns stats rather than the hero roster.

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?

There is no statement of when to use this versus 'opendota_heroes' or 'opendota_pro_matches', which are the obvious alternatives in the same namespace. The mention of 'per bracket' further implies a filtering dimension that isn't explained (and no parameter exists to select one).

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