who_should_i_target_next

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

With no annotations, the description carries the transparency burden. It usefully discloses that all parameters are optional with environment variable fallbacks, and that espn_s2 and swid are authentication cookies for private leagues. It also states the return type. However, it does not mention potential side effects, limitations, or the nature of the recommendation logic, leaving some behavior implicit.

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 well-structured with a clear one-sentence purpose, an Args list, and a Returns line. It is appropriately sized for a tool with 5 parameters. Minor repetition of the 'optional' pattern is acceptable but could be slightly tighter.

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?

The description covers all inputs and states the return is a dictionary with recommendation and reasoning, but there is no output schema and the return format is vague. It does not explain what factors drive the recommendation or how it relates to the sibling tools. Given the tool's complexity and lack of annotations, more detail on expected outputs and selection context would improve completeness.

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 schema provides no descriptions (0% coverage), so the description must compensate. It does so thoroughly, explaining every parameter (team_id, league_id, year, espn_s2, swid), including their types, optionality, environment variable fallbacks, and purpose. This is a strong addition beyond the bare 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 clearly states the tool's function: 'Get recommendation on which player to target/nominate next.' This provides a specific verb+resource combination that is distinct from siblings like get_free_agents or should_i_bid. However, it does not explicitly differentiate itself from similar analysis tools such as analyze_my_draft_strategy.

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 gives no guidance on when to use this tool versus alternatives. It does not mention suitable contexts, prerequisites, or exclusions. The name and brief description imply its use case, but there is no explicit direction.

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