get_double_gameweeks

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

No annotations are provided, so the description must fully disclose behavior. It states the tool returns 'information about double gameweeks and affected teams' but omits details like return format, pagination, or behavior when no double gameweeks exist. Minimal behavioral context.

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 concise, with one sentence for purpose and an Args section for parameter. It is front-loaded with the main action. Minor redundancy: the Args section essentially repeats the purpose but is acceptable for clarity.

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 low complexity (one optional param, no output schema), the description adequately covers the tool's purpose and parameter. However, it lacks return format details and error conditions, which would be helpful for an agent. Not fully complete but sufficient for basic usage.

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 input schema has 0% description coverage, so the description must compensate. It explains num_gameweeks as 'number of upcoming gameweeks to check' with a default of 5, adding meaning beyond the schema's title and type. However, it could clarify that this constrains the lookahead window.

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 'Get information about upcoming double gameweeks where teams play multiple times', which is a specific verb+resource combination. It distinguishes from sibling tools like get_blank_gameweeks and get_gameweek_status by focusing on double gameweeks.

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?

No guidance on when to use this tool versus alternatives. The description provides no context about when it is appropriate or inappropriate to call this function, nor does it mention related tools like get_blank_gameweeks that might be more suitable for certain queries.

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