wowaudit_get_attendance

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

The annotations clearly declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the tool's safety profile is well-covered. The description adds useful context about optional scoping but does not explain what 'attendance statistics' entail (e.g., format, counts, per-character). Since annotations already communicate the most critical behavioral traits, the description's added value is moderate but nontrivial.

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, front-loaded sentence that efficiently conveys the tool's purpose and optional filters. Every word adds value; there is no redundancy or filler. This is an excellent example of conciseness.

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 tool has 5 parameters (most optional), an output schema, and rich annotations, the description is somewhat minimal. It covers the core scoping options but does not explain what the attendance statistics contain or how to interpret the response. While the output schema may provide structure, the description could be more informative. This is adequate but not 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 description coverage is only 40%, meaning most parameters lack descriptions. The description mentions scoping by instance, encounter, and date range, which maps to the instance, encounter, startDate, and endDate parameters. However, the limit parameter's description is already in the schema (cadence 100%), so the description adds no further meaning. The encounter parameter's dependency on instance is covered in the schema description. Overall, the description only partially compensates for the low schema coverage.

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 clearly states that the tool retrieves attendance statistics, with optional scoping by instance, encounter, and date range. This makes the purpose clear and specific, distinguishing it from sibling tools that focus on teams, periods, characters, historical data, raids, wishlists, or loot history. A score of 5 is not given because the description does not explicitly contrast with siblings, though the domain is unique enough.

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 description indicates when to use optional filters (instance, encounter, date range) but does not provide explicit guidance on when to use this tool versus alternatives, such as wowaudit_list_historical_data or wowaudit_get_character_history. No exclusions or prerequisites are mentioned. This is a minimal viable score.

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