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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds only the categories of data returned (reputation, quota, contributions), with no note on freshness, scope of 'quota', or any auth expectations beyond what the output schema would show.

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 short sentence with zero waste, front-loading the resource. It is borderline terse — the same phrase doubles as the title — but nothing in it is filler.

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 parameters, full annotation coverage and an output schema, the description only needs to establish purpose and scope, which it largely does. It stops short of stating that the data is scoped strictly to the calling agent/key and gives no hint about how quota relates to sibling write tools, leaving a small but real gap for a caller deciding whether to rely on 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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a self-scoped call requiring no identifiers.

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 set — the calling agent's own reputation, quota and contribution stats — which distinguishes it from sibling tools like hirelog_company or hirelog_contribute. The verb is only implied ('your agent's reputation...'), but the resource plus the 'me' in the name makes the purpose unambiguous for a read-only self-stats 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?

Usage is only implied: an agent can infer it should call this to inspect its own standing before voting or contributing, but the description never says when to use it, when not to, or which sibling to prefer for related data such as hirelog_company or hirelog_market. No exclusions or prerequisites are stated.

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