opendota: Get player matches

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

Annotations (readOnlyHint, openWorldHint, idempotentHint) are already present and consistent. Description adds some behavioral context (returns recent matches with specified fields) but does not detail pagination, ordering, or return format. Adequate but not rich.

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?

Two sentences, no fluff. First sentence states purpose and content, second provides actionable usage tip. Efficient and well-structured.

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?

Output schema missing; description partially compensates by listing returned fields (hero, result, K/D/A, duration) but omits format (array), ordering, and date range specifics. Adequate for a straightforward list operation but not fully complete.

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% with descriptive parameter names and descriptions. Description does not add significant meaning beyond schema; only reiterates limit usage. Baseline 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?

Description clearly states 'Get a player's recent matches' and lists specific fields (hero, result, K/D/A, duration), distinguishing it from siblings like opendota_get_match (single match) or opendota_get_player_heroes (hero stats).

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?

Only provides a tip to use `limit` parameter; no explicit guidance on when to use this tool vs. alternatives or prerequisites. Lacks context for selection among similar sibling tools.

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