Waiver Claim

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

Annotations already indicate readOnlyHint=false, so the write nature is known. The description adds only that it's a waiver claim with optional drop, but doesn't disclose side effects like pending status, processing time, or failure conditions. With openWorldHint=true, more behavioral context is expected but missing. No contradiction with annotations.

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 sentences with zero redundancy. The core purpose is front-loaded, and the bid clarification is placed after. Every word earns its place.

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 claim tool with 8 parameters, the description covers the essential action but misses sibling differentiation (e.g., when to prefer add_free_agent) and doesn't mention that claims are processed asynchronously. Output schema exists, so return values are covered, but the context around claim lifecycle is incomplete.

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 50%, and the description compensates partially: it explains bid's league-type dependency and hints at the conditional drop. However, add_player_id, drop_player_id, and team_id are left undocumented in both schema and description, leaving gaps for a new agent.

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 states a clear verb and resource: 'Submit a waiver claim, optionally with a conditional drop.' This is specific and distinguishable from general roster actions. However, it doesn't explicitly contrast with sibling tools like add_free_agent, so it doesn't fully differentiate in purpose.

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 provides no guidance on when to use this tool versus alternatives such as add_free_agent or cancel_claim. It does offer a parameter-specific tip about bid usage in FAAB vs priority-waiver leagues, which is helpful for invoking correctly, but not for choosing the tool. No when-not-to-use or alternative references.

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