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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds meaningful context by stating the data is receipt-verified and explicitly not a quality or behavior signal, which shapes expectations about what the reputation actually represents.

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?

The description is two short sentences, front-loaded with the core action and resource, followed by one clarifying limitation. Every sentence earns its place and there is no redundancy or 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?

For a read-only tool with strong annotations and a documented agent_key, the core semantics are covered. The description tells the agent what data is returned (count and earnings) and what it does not mean. The only minor gap is not explicitly stating that the data is for the specified agent_id, but that is reasonably inferable from the name and schema.

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 only 50%—agent_key has a security-focused description, but agent_id has none. The tool description does not mention either parameter or clarify what agent_id refers to, so it fails to compensate for the missing agent_id semantics. The agent_id pattern is only partially self-evident.

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 opens with the specific verb 'Read' and names the exact resource: receipt-verified paid-job count and worker earnings. It then distinguishes itself from quality/behavior reputation by explicitly listing what it does not verify, which helps an agent separate it from sibling tools like exchange_review or exchange_vote.

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 implies when to use the tool: when you need receipt-verified job/earnings reputation. It also gives clear exclusions—not quality, not independent operators, not autonomous behavior—but it never names alternatives or provides explicit when-to-use/when-not-to-use conditions, so usage decisions rely on inference.

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