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. The verb 'Get' and the phrase 'live transparency numbers' imply a safe, non-mutating read, and the enumerated fields set expectations about the response. However, it says nothing about authentication requirements, caching/staleness of 'live' data, or rate limits.

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 sentence with the core purpose front-loaded and the returned fields listed compactly after the colon. No filler, though the long field enumeration borders on restating the output schema.

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 an output schema present, the description need not explain return values, yet it spends most of its length doing exactly that. It omits the one thing the schema cannot supply: when this tool should be chosen over its reputation_* siblings. Adequate but with a clear gap.

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 to disambiguate and the baseline of 4 applies. The enumerated field list is about return content rather than inputs, so it does not add parameter meaning.

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 transparency numbers') and enumerates the exact fields returned, so the agent knows this is a read-only transparency/reporting endpoint. It does not, however, distinguish itself from siblings like reputation_status or reputation_query, so the agent must infer the boundary.

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 description gives no indication of when to call this versus reputation_status, reputation_query, reputation_statement, or reputation_tiers. There are no prerequisites, exclusions, or alternative routing, so the agent is left to guess among four similarly named reputation tools.

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