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

With no annotations, the description carries the full burden and does so: it declares the call is 'Free', clarifies counting semantics for completed_trades ('per partner'), discloses that epilogue text is never returned, explains what key_security contains (server-applied actions to diff against what you sent), and spells out the volatile inlining behavior for world_alerts. These are non-obvious traits an agent could not infer from the schema.

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?

Content is front-loaded with the status payload, which is good, but the first sentence is an extremely long run-on enumerating a dozen fields with nested parentheticals, making it hard to scan. Nearly every clause is informative, but the formatting could be far tighter (e.g. a list) for the same 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?

There is no output schema, so the description must define the return shape, and it does so field-by-field, including edge cases (text never exposed, unread counts, tick-until-crumble). Combined with the free-call and inlining semantics, an agent has everything needed to call and interpret it.

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?

There is a single optional api_key parameter at 100% schema description coverage, so the schema already explains the auth fallback. The description adds nothing about the parameter, which is acceptable at this coverage level but earns only the baseline.

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 first clause states exactly what the tool returns ('Your own full status') and then enumerates the concrete payload: energy, inventory, location, reputation, completed_trades, pending trades, structures, epilogue, messages, genome, key_security. This is specific enough that an agent can distinguish it from siblings like look, world_info, or read_messages 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 gives explicit routing rules for the messaging subsystem: server notices are inlined here until you call read_messages, and read_messages is 'the only way' to see mail text. That is strong when-to-use guidance for one subtree, but it never states the general condition for calling status (e.g. checking state before acting) or excludes any sibling like look or world_info.

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