set_level

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

The description indicates the tool mutates state ('Set') and returns updated stats, which is positive. However, without annotations, it does not disclose potential side effects, validation rules, or whether the level change impacts other attributes beyond stats.

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 concise sentence (12 words) that front-loads the action and key constraint. Every word adds value—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?

Given the low complexity (one parameter) and presence of an output schema, the description is largely complete. It covers the essential constraint (range) and return behavior. Minor omission: it could note that setting level affects the build's stat calculations.

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 schema provides only the parameter name and type, but the description adds the valid range '1-100', which is crucial for correct invocation. This compensates for the 0% schema description coverage.

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 clearly states the action ('Set'), the resource ('active build's character level'), and the valid range ('1-100'). It also mentions the return value ('Returns updated stats'), which helps distinguish it from sibling tools like set_class or set_skill.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't indicate that level should be set before or after other configuration, or any prerequisites like having an active build.

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