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

No annotations are provided, so the description carries the disclosure burden; 'snapshot' implies a read-only, non-mutating call, which is useful but not stated outright. It omits auth/scope context (the schema notes a scope requirement) and says nothing about freshness or caching, though for a trivial self-read that is a minor 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?

A single economical sentence that front-loads the identity ('your own progress snapshot') followed by the payload. Nothing is wasted, though it is arguably under-explained rather than optimally sized.

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 and no annotations, the description compensates by enumerating exactly what the snapshot contains, which is the key information an agent needs. Missing only the when-to-use routing and any auth note.

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% and the single api_key parameter is fully documented in the schema, including its deprecated header fallback. The description adds no parameter information, so the baseline of 3 applies.

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 names a specific resource ('your own progress') and enumerates the returned fields (level, Vorn Score, streak, rank, credit balance), so an agent can tell this is a personal-stats read. It doesn't explicitly contrast itself with the sibling economy_summary, which covers overlapping balance data, leaving some ambiguity about which to call.

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 economy_summary or evaluations_mine, nor any preconditions. Usage is only implied by the word 'your own'.

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