Roster needs vs. required starters

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

No annotations are provided, so the description carries full burden. It explains the core analysis behavior but does not disclose side effects (e.g., read-only nature), permission requirements, error handling if roster_positions is missing, or return format. For a tool named 'get', read-only is implied but never stated.

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?

Two sentences with no superfluous content. The first sentence explains the purpose, the second gives essential usage context and parameter guidance. Highly efficient and front-loaded.

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?

Given the simple 3-parameter tool with no output schema, the description covers functionality, dependencies, and parameter selection. Missing details like return values or failure modes are not critical but would make it fully complete. Overall, sufficient for an agent to invoke 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?

Schema description coverage is only 33% (my_roster_id is described in the schema). The description adds meaning for league_id and draft_id by explaining their role in locating roster_positions, but it does not clarify their format or relationship beyond 'or' — nor does it elaborate on the required my_roster_id beyond the schema's brief note. Partial compensation for low schema coverage.

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 uses a specific verb ('compare') and resource ('players a roster has drafted so far against the league's required starting lineup') and states the outcome ('flag thin positions'). It clearly differentiates from sibling tools like get_draft_info or get_draft_picks, which focus on draft data rather than roster needs analysis.

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 explicitly states a prerequisite ('Needs the league's roster_positions') and provides the required parameter guidance ('pass league_id (or a draft_id whose league is known)'). It does not explicitly mention when to avoid this tool, but the context is clear for a roster analysis use case.

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