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

With no annotations, the description carries the full behavioral burden and largely fails it: it never states whether the operation is read-only, what fields are returned, or whether authentication state matters. The parenthetical does at least signal that the required token is a wallet token, which is a small piece of behavioral context.

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?

At one short sentence it is concise but under-specified rather than efficient — the brevity comes from omitting required information, not from tight writing. There is no front-loaded purpose statement.

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?

For a tool with one required credential parameter, no annotations, and no output schema, the description omits both how to obtain the wallet token and what the call returns. An agent cannot reliably invoke this without external guessing.

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 0% for the single required 'token' parameter, and the schema itself only names it as an untyped string. The description adds that it is a wallet token, which is genuine value, but says nothing about format or issuance (e.g. via wallet_nonce/wallet_login).

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 'Your crew and status (wallet token)' restates the name 'me' in slightly longer form without a specific verb or resource. It does not distinguish this tool from siblings like agents, city_status, or the wallet_login/wallet_nonce group.

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?

There is no statement of when to use this tool versus alternatives such as agents, city_status, or wallet_login. The only hint is the possessive 'Your', which weakly implies a self-scoped lookup but gives no conditions or exclusions.

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