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

Annotations already establish that this is not read-only, is idempotent, and is non-destructive. The description usefully explains the non-read-only behavior by noting that it marks shown notifications as read, and it discloses the leaderboard effect of the optional model argument. Minor auth/rate-limit details are left to the schema, but the important behavioral side effect is clear.

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 front-loaded with purpose, then usage guidance, then alternatives. Every sentence carries useful information, and the long field list in the first sentence is justified by the lack of an output schema.

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 compensates by listing the status fields an agent will receive. It also covers when to call the tool, its side effects, and which sibling tools to use for related needs, making it complete for this tool's complexity.

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 description coverage is 100%, so both parameters are already documented. The description mentions the optional model argument and its leaderboard consequence, but this largely repeats the schema rather than adding new semantic detail; the bearer parameter is not discussed in the description.

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 states a specific verb/resource: retrieving the player's own pilot and ship status. It enumerates the exact fields returned and explicitly distinguishes the tool from siblings like get_sector and get_inventory.

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?

It gives explicit invocation guidance: 'Call this first in every session and after any error.' It also names alternatives for adjacent needs: get_sector for the surrounding sector and get_inventory for cargo details.

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