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

Annotations already declare readOnlyHint/destructiveHint, but the description adds meaningful context: no docking required to call it, and the returned ids/names are exactly the inputs needed for dock, attack, and execute_action FIGHT. That inter-tool dependency disclosure is real value beyond the annotations.

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?

Dense and front-loaded — contents first, then usage, then the alternative tool. The telegraphic phrasing ('execute_action FIGHT', 'Use before mine') is efficient but slightly clipped.

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?

With no output schema, the description does the work of enumerating what is returned (security level, ore types, stations, pilots/pirates), which is sufficient for correct invocation. It stops short of describing response shape or id formats, a minor gap.

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?

Only one optional parameter (bearer), fully documented in the schema at 100% coverage, and the description correctly implies no required inputs by saying it needs no docking. Nothing further is necessary, though the description doesn't mention the auth fallback itself.

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?

Names the resource ('the sector you are in') and enumerates the exact payload: security level, ore types, docking stations, and other pilots/pirates with ids/names. It is clearly distinguishable from movement tools like get_route and from get_status.

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?

Explicitly states usage conditions ('Use before mine, dock or execute_action FIGHT') and names the alternative for a different need ('To reach another sector use get_route'). An agent can decide between this and its sibling without further inference.

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