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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered structurally; the description still adds value by stating the action is damaging and not reversible and that a combat result is returned. It does not cover failure modes (target absent from sector, cooldowns, death consequences), which keeps it below a 5.

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?

Three tight clauses with the highest-stakes disambiguation (PvP vs PvE) front-loaded, followed by the consequence and return signal. No filler sentences; every clause carries routing or behavioral information.

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 the description notes a combat result is returned and states the key precondition (target in current sector). Missing detail on error cases and whether the attacker can be destroyed in return, which matters for a destructive PvP action.

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 100%, so both parameters are already documented, including the bearer fallback. The description only reinforces that targeting is by exact username and that the target must be in the current sector — useful but essentially duplicative of the schema. Baseline 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?

States a specific verb (attack) and resource (another PLAYER pilot) plus the scoping mechanism (target_username, same sector). It explicitly excludes the pirate/PvE case, which is the closest sibling path (execute_action action=FIGHT), so the agent can separate the two without opening schemas.

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?

Gives explicit when-to-use (PvP against a player pilot in your sector) and when-not-to-use (pirates are attacked via execute_action action=FIGHT, optionally with pirate_id), naming the alternative tool and the condition that selects it.

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