Set daily lineup

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

The description explicitly labels the tool as 'DESTRUCTIVE' and explains that it modifies real Yahoo roster positions. It goes beyond the annotations by stating that unlisted players keep their current slot and that defaults are used. 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 three sentences, each carrying essential information: the destructive nature, how to use assignments, and the confirmation requirement. No redundant words.

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 annotations cover destructiveness, and the schema documents all parameters, the description is complete. No output schema is present, but the description doesn't need to explain return values as it is not provided.

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 100%, so baseline is 3. The description adds context such as 'Players not listed keep their current slot' and explains the mapping of playerKey to position, which is helpful beyond the schema descriptions.

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 starts with 'changes your real Yahoo roster positions for a given date,' clearly identifying the verb 'changes' and the resource 'roster positions'. This distinguishes it from sibling tools like add_drop_player or get_team_roster, which serve different purposes.

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 instructs to 'Confirm the lineup with the user before calling this,' providing a clear usage guideline. It also explains the default behavior for date and team key, and the mapping of assignments. It does not explicitly list when not to use or compare to alternatives, but the destructive hint and the instruction to confirm suffice.

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