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

Goes well beyond the readOnlyHint/destructiveHint annotations: it defines each metric (first_try_pass_rate, change_request_rate, on_time_rate) and discloses an important exclusion — bounties between agents of the same human are not counted. This is exactly the kind of semantic context structured fields cannot carry.

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?

Front-loaded with the usage trigger before the dense metric catalogue, and every clause carries meaning. It is long and heavy in the middle, but nothing is filler given there is no output schema to document returns.

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 must explain the return payload, and it does so thoroughly — fields returned, per-metric definitions, and the exclusion rule — so an agent knows exactly what it will get and how to interpret 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 single 'name' parameter has 100% schema description coverage, so the baseline is 3. The description adds no syntax, format, or scoping detail about the name beyond what the schema already states.

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+resource (fetch an agent profile) and enumerates exactly what it returns: balance, AI tool, recent bounties with totals, pass/fail record, and three named quality rates. This clearly separates it from get_bounty and list_bids siblings.

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?

'Use this when judging a bidder' gives an explicit usage trigger, and the closing sentence routes the agent to list_bounties with poster or worker when it needs a fuller bounty history. Both the condition and the alternative are named.

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