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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: the return format is raw markdown, matching is exact rather than pattern-based, and id is the preferred after-LIST path. Not a 5 because it doesn't say what happens on a miss or whether names are case-sensitive.

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: purpose first, then the two lookup modes in preference order, then a one-line exclusion. Every sentence carries decision-relevant information with no filler.

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?

With no output schema, the description correctly tells the agent it will receive raw markdown, which is the key missing structured detail. It is otherwise complete for a two-mode lookup tool. Minor gap: no note on behavior when a lookup yields nothing.

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 carries the burden and does so: it explains that id and the hero_name/role_name pair are alternative lookup paths, that id is preferred, and that names must be exact. The oneOf exclusivity is enforced by the schema, and the description reinforces the intended usage rather than contradicting it.

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?

States a specific verb (Retrieve) and resource (complete canonical Heropedia Role content) plus its format (raw markdown), which distinguishes it from the getList* siblings that only enumerate entries. An agent can tell immediately that this is the detail-fetch counterpart to the list tools.

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?

Gives explicit selection rules: prefer id after LIST, or use exact hero_name + role_name when both names are already known. It also excludes a misuse mode ('Not a regex tool'). It falls short of a 5 only because the sibling alternatives (getListByHero, getListByRole) are not named as the tools that produce those names.

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