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

No annotations are provided, so the description carries full burden, and it delivers real behavioral context beyond the schema: the values are live and admin-configurable, so callers must fetch them rather than cache assumptions. It omits auth/permission requirements and rate-limit behavior for the caller, which keeps it from a 5.

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 purpose and followed by the key usage constraint, with the enumerated return fields in a compact parenthetical. No wasted words.

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?

An output schema exists, so return values need no further explanation, and the description already names the key fields anyway. Purpose plus the live/configurable behavioral note is everything an agent needs to call this zero-param getter correctly.

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 schema-side baseline is 4. The description lists the returned fields rather than parameter semantics, which is appropriate and adds no confusion.

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?

States a specific verb (Get) and resource (Wicked Reputation's live tier thresholds and benefits) and enumerates exactly what is returned. An agent can distinguish this from siblings like reputation_query or reputation_status without opening either schema.

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?

The clause 'Read at call time rather than assumed' gives clear guidance on when to invoke it: whenever current thresholds matter, because they are admin-configurable. It stops short of naming alternative siblings or explicit exclusions, but the usage directive is unambiguous.

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