set_wanted_level

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

No annotations are present. The description states 'apply it' implying immediate effect, but does not disclose potential side effects like triggering police or interaction with other game systems.

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?

Two concise sentences that front-load the main action and range, with zero wasted words.

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-parameter tool with an output schema (not shown but present), the description covers the essential input and intended effect. Could mention what happens if level is out of range, but overall sufficient.

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 has 0% description coverage, but the description adds the range (0-5) which is missing from the schema. Also explains the special meaning of 0 for clearing stars, compensating for the schema's lack of constraints.

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?

Clearly states the verb 'Set' and resource 'wanted level' with a specific range (0-5). Distinguishes itself from sibling tools like set_health or set_invincible by its unique focus on wanted level.

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?

Provides a specific usage tip: 'Use 0 to clear stars.' While it doesn't explicitly mention when not to use, the context is clear for this simple game mechanic.

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