get_jungle_summary

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It fails to describe what the summary includes, how it is structured, whether it is read-only, or any side effects. The description provides only a high-level action without behavioral details.

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?

The description is a single, concise sentence that conveys the core purpose without extraneous words. It is appropriately sized and front-loaded with the key verb and resource.

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?

The tool has a very simple interface (one parameter) and an output schema exists, so the description need not explain return values. However, the lack of usage guidance and behavioral transparency makes the description incomplete for an agent to properly decide when and how to use it, especially among many similar sibling tools.

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% and the description does not mention match_id at all. Although match_id is self-explanatory in the schema, the description adds no value beyond the parameter name, and with zero coverage it fails to compensate for the lack of schema descriptions.

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?

The description states the purpose clearly with a specific verb ('Get'), resource ('jungle activity summary'), and scope ('for a Dota 2 match'). It differentiates from sibling tools like get_lane_summary by specifying 'jungle' instead of 'lane'.

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 usage context is implied: this tool is for obtaining a jungle activity summary for a specific match. However, there is no explicit guidance on when to use this versus alternatives like get_lane_summary or get_farming_pattern, nor any exclusions or prerequisites.

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