Find heroes by power

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It clearly states substring matching rather than exact matching and that every matching hero is returned, which also implies a read-only operation. It does not cover case-sensitivity or edge cases, but these are minor for a simple query.

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?

One concise sentence conveys the verb, resource, matching behavior, and an example. There is no filler or redundant detail.

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 single-parameter lookup tool with an output schema, the description is largely complete: an agent knows what the tool does, what the parameter means, and what kind of result to expect. It could be improved by naming alternatives or clarifying matching case-sensitivity, but these are not blockng for correct invocation.

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?

The input schema provides only a 'Power' field with no description (0% coverage). The description compensates by explaining that the parameter is a substring matched against hero power lists, with the example 'flight'. This adds meaningful semantics, though it does not specify case sensitivity.

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?

Uses a specific verb ('Return') with a clear resource ('hero') and a precise matching rule ('power list matches the given substring'). This distinguishes it from sibling tools like list_heroes or get_hero, even without naming them.

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 when to use the tool: when you need heroes by a power substring. However, it does not explicitly mention alternatives or state when not to use it, leaving routing to inference among siblings like list_heroes and get_hero.

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