evaluate_add_drop

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is known. The description adds useful output context (category deltas and before/after matchup odds), but says nothing about whether lineup/roster state must be current, whether it mutates anything implicitly, or what inputs are required.

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?

A single dense sentence with the core action front-loaded and the parenthetical scoping the drop case economically. Nothing is wasted, though the nested clauses make it slightly harder to parse than a two-sentence split would.

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 and 0% schema description coverage, the description does the right thing by summarizing the return values. However, for a 3-parameter tool it leaves the required/optional distinction and input format entirely unstated, which is a meaningful gap for correct invocation.

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 0%, so the description carries the burden. It does convey the semantics of all three parameters – 'add' a free agent, 'drop' one of mine, and the matchup context for 'opponent' – but supplies no format detail (player names vs. IDs, whether opponent is required or optional) to compensate for the empty schema.

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 names a specific verb (quantify) and resource (adding a free agent while dropping one of mine) and states the computed outputs: rest-of-season G deltas by category plus matchup odds before/after. It does not, however, distinguish itself from siblings like evaluate_trade, waiver_decision, or find_trades, which an agent must disambiguate on its own.

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?

Usage is implied by the wording – it is clearly a pre-move add/drop analysis tool – but there is no explicit when-to-use guidance, no exclusions, and no routing to the obvious alternatives (waiver_decision, evaluate_trade, free_agents). The agent must infer the situation from the name and description alone.

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