Get hero

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

No annotations are provided, so the description carries the full burden. It discloses that the operation is a non-mutating lookup returning the full record, but it does not describe behavior for unknown codenames, case sensitivity, or error conditions. This is adequate but not rich.

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 a single, front-loaded sentence with no filler. Every word contributes meaning, and the example is useful without bloating the text.

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 single-record getter with one parameter and an output schema, the description is mostly complete. It clearly tells the agent what input to provide and what to expect. A small gap is not noting how to discover valid codenames (e.g., via list_heroes), but this is not essential for calling 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 coverage is 0%, but the description compensates by explaining that the only parameter, codename, is the hero's identifier, and provides a concrete example. This adds real meaning beyond the schema's bare 'Codename' title.

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 ('Return'), a specific resource ('full record for one hero'), and a clear identifier ('by codename'). It distinguishes itself from siblings like list_heroes (which would return multiple) and hero_bio (which implies a focused bio, not a full record).

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 clearly implies this tool is for fetching a single hero when the codename is known, giving an example ('spider-man'). It does not explicitly state when to use alternatives such as list_heroes or find_heroes_by_power, but the context is clear enough for an agent to select it appropriately.

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