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

Annotations already cover safety (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the description adds value by disclosing pagination behavior, the exact returned fields, and the explicit exclusion of full Role prompts. This is especially useful given the absence of an output schema.

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 two sentences, front-loaded with the action and resource, then provides return details and a key exclusion. Every sentence earns its place with no redundant wording.

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 simple read-only, paginated listing tool with safety annotations, the description covers the return fields and a notable exclusion. It does not specify the exact response envelope (e.g., array of objects), but the given metadata list and schema constraints make the tool adequately invocable.

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 bears the burden, but it only says 'using pagination' without explaining page/page_size meaning. The parameter names, types, defaults, and ranges in the schema make the intent reasonably clear, but the description does not add meaningful extra semantics.

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 ('List') and resource ('Heropedia Hero/Role entries'), and clarifies that it returns lightweight metadata, distinguishing it from detail or filtered-list siblings like getDetail, getListByHero, and getListByRole.

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 a general paginated listing use case and mentions that full Role prompts are not returned, but it does not explicitly name alternatives or state when to prefer getDetail or getListByHero/getListByRole. Usage context is present but routing is left to inference.

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