get_trade_candidates

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

No annotations are provided, so the description carries the full burden, and it does substantial work: it discloses the internal algorithm (weakest starting position group, other teams' bench/surplus depth) and what the response groups by, including that the owning team is included so the user knows whom to approach. It omits nothing critical for a read-only lookup 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?

One-line purpose up front, followed by the Args detail and then the mechanism. Efficient and front-loaded. The Args block slightly restates the schema, but it is short and matches convention.

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?

An output schema exists, so return formatting needn't be explained, yet the description still sketches the grouping structure. Combined with the fuzzy-parameter note and the algorithmic disclosure, an agent has enough to call this correctly and interpret the result.

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 coverage is 0% and the single parameter's schema only says type string. The description compensates by clarifying that team_name accepts a team name OR an owner name and that matching is fuzzy — meaningful semantics the schema does not carry.

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 and resource ('Identify potential trade targets for a team') and then explains the mechanism: find weakest starting position group, scan other teams for bench/surplus players. That is far more than a name restatement. It doesn't explicitly distinguish itself from the similarly-named sibling get_trade_activity, but the purpose is unambiguous.

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 makes the use case implied — you call this when you want trade targets — but never states when to prefer it over siblings like get_trade_activity (past trades), get_free_agents, or get_team_analysis. There is no explicit when/when-not guidance.

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