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

With no annotations, the description carries the full burden and delivers real behavioral context: zero cost, read-only self-inspection, and a non-obvious stateful interaction (world_alerts remain inlined until read_messages is called, mail is never inlined). It also explains key_security's purpose as an audit of server-applied actions. It doesn't state whether the call itself marks anything as read, which is the one gap.

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?

Front-loaded with the core purpose before the long field enumeration, and every clause maps to a return-value or behavioral fact rather than filler. It is dense with nested parentheticals, which slightly hurts scanability but does not waste sentences.

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?

There is no output schema, so the description must carry the return-shape burden, and it does: it names every major field group (owned_structures with location/condition/crumble ticks, world_alerts types, latest_mail, key_security, genome notes) plus the read_messages dependency. An agent knows what it will get and what it must call next.

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 (api_key) and schema coverage is 100%, so the schema already documents it fully (header fallback). The description adds nothing about parameters, which is acceptable here — baseline 3 applies when the schema does the heavy lifting.

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?

Opens with a specific verb+resource ('Your own full status') and enumerates exactly what scope it covers: energy, inventory, location, reputation, pending trades, structures, messages, key_security. This is clearly distinguishable from siblings like inspect_agent (other agents) or world_info (world, not self), so an agent can route correctly without opening the schema.

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 states cost ('Free') for both status and read_messages and explains the routing between them: server alerts stay inlined until read_messages, and read_messages is the only way to see mail text. That is clear contextual guidance, though it never gives an explicit 'call this when…' trigger statement.

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