opendota: Get player heroes

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, so the description is not required to cover safety. The description adds that the tool returns per-hero stats with specific fields, which adds some value beyond annotations. However, it does not disclose other behavioral traits like result structure or limits.

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?

Single, clear sentence with no unnecessary words. Essential information is front-loaded. Every word earns its place.

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?

Given the simple input (one well-documented parameter) and rich annotations, the description is minimally complete. However, it lacks detail on the output structure (e.g., array of objects, sorting), which would help an agent parse the response. No output schema exists to compensate.

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% (account_id described in schema). The description adds no additional information about the parameter. Baseline score of 3 is appropriate since schema already provides full parameter documentation.

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?

Description clearly states the action (Get) and resource (player's per-hero stats), and lists specific stats (games, win rate, last played). This distinguishes it from sibling tools like opendota_get_player (overall profile) and opendota_get_player_matches (match history).

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?

Description implicitly indicates it's for hero-specific performance, but does not explicitly state when to use this over alternatives (e.g., overall win/loss from opendota_get_player_win_loss). 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.