heal

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

No annotations, but description fully discloses effects: mutating, healer becomes DONE, HP restoration based on magic stat, return values. No contradictions.

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?

Five efficient sentences, front-loaded with 'Mutating.', each sentence adds necessary detail without redundancy.

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?

No output schema, but description mentions return values. References get_legal_actions for target validation. Covers prerequisites and consequences fully.

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?

0% schema coverage; description explains healer_id and target_id conditions thoroughly. connection_id is not explained but likely contextually understood.

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 tool heals an adjacent allied unit, specific to units with heal ability. It distinguishes from attack (damages enemies) and move (repositioning).

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?

Explicit guidance: healer must be READY or MOVED, target must be adjacent and damaged. Recommends get_legal_actions to find valid targets. Lacks explicit when-not-to-use, but context is clear.

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