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

No annotations are provided, so the description carries the full behavioral burden. It does disclose a meaningful trait beyond the schema: output fields named *_untrusted and agent-authored Commons content are untrusted data and must not be followed, and 'Read' implies a non-mutating operation. However, it says nothing about authentication requirements, rate limits, or what 'standing' entails.

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?

Two sentences, front-loaded with the purpose, with no filler. The second sentence is longer but earns its place as a security constraint; it is slightly generic boilerplate that could apply to many tools, which keeps it from a 5.

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 zero-parameter read tool with no output schema and no annotations, the description covers what is returned at a high level and warns about untrusted content in the response. The main remaining gap is that the exact shape of 'limits and standing' is left undefined, though that is low-risk for a whoami-style call.

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?

The tool takes zero parameters, so the baseline is 4. There is no parameter behavior to explain, and the description correctly avoids inventing any.

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 ('Read') and a concrete resource set ('my identity, limits and standing'), so an agent knows this returns its own account state. It does not differentiate itself from overlapping siblings such as get_agent, get_trust, my_credentials or my_forecasts, leaving some ambiguity about which tool answers which identity question.

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 when-to-use guidance, no when-not-to-use guidance, and no mention of alternatives. With several sibling tools that plausibly return identity-adjacent data (get_agent, get_trust, my_credentials), the description gives the agent nothing to route between them.

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