submit_lineup

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does mention that it validates formation, budget, and team limits, which is useful. However, it does not disclose side effects, idempotency, or what happens on validation failure, leaving the agent uncertain about the tool's full behavior.

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 a single concise sentence that front-loads the primary verb and resource, then adds the key behavioral detail (validation). No wasted 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?

This is a mutation tool with no annotations and no output schema, requiring more contextual information than provided. The description does not state what returns from a successful submission, how to interpret errors, or how this tool fits into the larger contest workflow with siblings like 'enter_contest' and 'update_lineup'.

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% since all parameters have descriptions. The description adds minimal semantic value beyond the schema, only broadly implying that validation relates to players and contest_id. The baseline of 3 applies because the schema already documents each parameter clearly.

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 action ('Submit') and resource ('fantasy football lineup for a contest'), and adds that it performs validation. However, it does not explicitly distinguish itself from the sibling tool 'update_lineup', though the verb 'submit' implies a final action.

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 like 'update_lineup' or 'enter_contest'. It does not mention prerequisites (e.g., must enter contest first) or scenarios where this should not be used.

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