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

Annotations already declare read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds that the regex is case-insensitive and limited to a safe subset, plus a note about lightweight metadata, which is useful. However, it doesn't describe pagination behavior or rate limits, leaving some behavioral gaps.

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?

Three tight sentences that front-load the core action and include only essential constraints. Every sentence adds value without redundancy.

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's simplicity (3 params, no output schema, rich annotations), the description covers the essential purpose and regex behavior. It could mention pagination defaults or how to use page/page_size, but overall it is sufficient for an agent to call the tool correctly.

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%, so the description must compensate. It explains the hero_regex parameter well (case-insensitive, safe subset) but provides no information about the page and page_size parameters, which are left entirely to the schema. Baseline 3 reflects partial compensation for the coverage gap.

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 a specific verb+resource: it lists Hero/Role entries filtered by hero name regex. It is clear about what it returns, though it doesn't explicitly differentiate from sibling tools like getListByRole or getDetail beyond implying a name-based lookup.

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?

It gives clear context: 'Use when you know or can identify the Hero and want to inspect that Hero's available Roles.' This implicitly distinguishes it from role-based lookup (getListByRole) and detail (getDetail), but doesn't name alternatives or exclusion conditions.

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