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

The annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful context beyond that: case-insensitive regex, a restricted 'safe subset', and lightweight metadata returns. This adds behavioral detail without contradicting 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?

Three short sentences carry distinct information: purpose, usage trigger, and behavioral caveats. There is slight redundancy between 'List ... matches the supplied regex' and 'inspect Heroes offering a particular Role', preventing a perfect score.

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?

For a read-only list tool with annotations covering safety, the description gives filtering semantics, regex behavior, and return nature ('lightweight metadata'). Missing explicit pagination guidance and sibling routing are minor given the schema defaults and simple tool shape.

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 role_regex semantics well ('matches', case-insensitive, safe subset), but says nothing about page or page_size; those rely on their self-evident names and schema defaults/min/max. This is adequate but incomplete.

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 action and resource: 'List Heropedia Hero/Role entries whose Role name matches the supplied regex.' The role-focused filter makes it semantically distinct from the sibling getListByHero, but it does not explicitly name alternatives, so it falls short of full differentiation.

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?

'Use when you want to inspect Heroes offering a particular Role' provides a clear and explicit trigger for using this tool. It does not state when-not-to-use conditions or point to alternatives, which keeps this at a 4 rather than a 5.

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