pending_offers

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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds real behavioral context beyond them: each incoming offer is evaluated from the user's side with a verdict and category deltas, writes are out of scope, and the demo league returns a message rather than data. That is meaningful disclosure for a read tool.

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?

Three short sentences, front-loaded with the resource before the behavioral detail. The trailing 'Demo league: a message.' is slightly cryptic but adds a concrete behavioral note rather than padding.

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 parameters and no output schema, the description carries the return-value burden and does so adequately by naming verdict and expected-category deltas. Combined with the scope note, an agent has enough to call and interpret the tool 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, which per the rubric sets the baseline at 4. Schema coverage is 100% and there is nothing for the description to clarify.

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 resource (pending trades and waiver claims) and implies a list/retrieve verb, plus it clarifies the evaluation angle (verdict, expected-category deltas). It does not explicitly differentiate from siblings like list_proposals, get_proposal, or evaluate_trade, so an 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?

It implies usage context (viewing your own pending offers) and usefully constrains scope by noting accept/reject are manual in the Yahoo app and writes are out of scope. However, it never names an alternative or states when to prefer another tool over this one, so routing is left to inference.

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