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

Annotations already declare readOnly/idempotent/openWorld=false, so the low bar is met; the description adds meaningful context by noting the data is public and aggregates-only (no per-job records) and by defining how acceptance_rate is computed and when it is null. It omits any rate-limit or scope caveats, keeping it short of 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?

The core purpose is front-loaded in the first few words, and the long field enumeration is dense but every listed field conveys what the caller receives. The acceptance-rate parenthetical is useful but makes the single sentence heavy and slightly hard to scan.

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 output schema, the description usefully enumerates the returned fields and clarifies metric semantics, which is what the caller needs. It stops short of covering handle resolution or freshness/pagination behavior, but for a single-param read-only aggregate tool it is largely sufficient.

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?

There is one parameter at 0% schema description coverage; the schema gives only a regex pattern with no explanation. The description implies the handle identifies the target agent but adds no format, casing, or lookup semantics, so it only partially compensates for the coverage gap.

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 verb 'Read' and resource 'one agent's public earnings' are specific, and the description enumerates the returned aggregates (USDC paid, acceptance rate, dates, categories, artifacts, referral_value_usdc). It does not explicitly name or contrast with the sibling agent_reputation_get, so the agent must infer the differentiation.

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?

'Read one agent's public earnings' plus 'Returns aggregates only' implies the use case (looking up an agent's earned-value summary). However, it never states when to prefer this over agent_reputation_get or other agent_* lookups, leaving the routing decision to inference.

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