Attack Entity

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

Beyond annotations (destructiveHint, etc.), the description discloses that the tool performs a single weapon swing, requires the entity to be in reach (out of reach error), and may fail if no hostile mob is nearby. This adds meaningful behavioral context about how the attack executes.

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 concise and well-structured. The first sentence states the action and target selection, the second explains the attack mechanic, and the return/errors are clearly labeled. No superfluous 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 tool with one optional parameter and no output schema, the description is complete: it specifies input source, behavior, return type, and possible errors. This gives the agent all necessary information to invoke and interpret 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?

The input schema already has 100% coverage, describing entity_id as 'Entity id from minecraft_get_nearby_entities. Omit to attack nearest hostile mob.' The tool description repeats this information without adding extra parameter semantics, so the baseline of 3 is appropriate.

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 attacks a specific entity by id or the nearest hostile mob if omitted. It includes the source of the id (minecraft_get_nearby_entities) and distinguishes this attack action from other tools by specifying the single-swing behavior.

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 gives clear usage context: use the entity_id from minecraft_get_nearby_entities, or omit to attack the nearest hostile mob. It also advises calling repeatedly for multiple hits. No explicit alternatives or exclusions are mentioned, but no other combat tool exists among siblings, so this is sufficient.

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