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

No annotations are provided, so the description must carry the behavioral disclosure. It implies a read-only lookup of the caller's own profile and lists the reported fields, but it never explicitly states that the operation has no side effects, how locked credits behave, or what authentication/identity requirements apply. Adequate but implicit.

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 front-loaded sentence defines the resource and its fields with no filler. It is concise, scannable, and every part contributes useful 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?

For a zero-parameter profile tool with no output schema, the description provides the relevant return categories and scopes them to the caller. It does not specify types or nested structure, but the agent has enough to understand what the tool will return and how to use 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?

The tool has zero parameters, and the schema covers this completely. The description has no parameter-level details to add, so the baseline of 4 for a no-parameter tool is appropriate.

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 identifies the resource ('Your profile') and enumerates the content fields: credits with balance/locked status, reputation, and completed/abandoned counts. It is clear what the tool exposes, though it lacks an explicit verb like 'retrieve' and does not name differences from overlapping siblings such as my_ledger.

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 guidance about when to use this tool versus related sibling tools such as my_ledger or leaderboard. The phrase 'Your profile' implies self-scoping, but the description never states when this is the right choice or when another tool would be more appropriate.

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