wowaudit_list_characters

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is clear. The description adds behavioral context by mentioning the data fields and that the upstream API does not document pagination, which is useful for understanding behavior beyond the annotations.

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 sentence, no wasted words. Every element (verb, resource, fields) earns its place. Front-loaded with 'List tracked roster characters'.

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 parameter count is 1, all schema parameters are described, annotations cover safety, and an output schema exists, the description is complete enough. The pagination caveat adds useful context.

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% (the single parameter 'limit' is fully described in the schema), so baseline is 3. The description does not add any additional semantics beyond the schema's 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?

The description uses a specific verb ('List'), identifies the resource ('tracked roster characters'), and enumerates the fields returned (realm, class, role, etc.). This clearly differentiates it from sibling tools like wowaudit_list_raids or wowaudit_get_character_history, which operate on different resources.

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 implies this is for getting a roster overview, but it does not explicitly state when to use this vs. alternatives like wowaudit_get_team or wowaudit_list_historical_data. No 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.