fpl_get_current_gameweek

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

Annotations already declare readOnlyHint and idempotentHint, indicating a safe read operation. The description adds value by explaining the behavior: returns active or upcoming gameweek, and details error cases. 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 well-organized with sections for Args, Returns, Examples, and Error Handling. It is informative without being overly verbose, though the error handling details could be condensed for even greater conciseness. This is a minor nuance.

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 tool's simplicity (one parameter, read-only, output schema exists), the description is complete. It covers what the tool does, how to use it, return information, and error scenarios. No gaps are apparent.

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 description thoroughly documents the single parameter (response_format), including default and possible values ('markdown' or 'json') with examples. Although the input schema also provides descriptions, the description enhances understanding with practical usage guidance beyond schema metadata.

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 retrieves 'the current or upcoming Fantasy Premier League gameweek information.' It specifies the exact resource (gameweek) and the verb (get), and distinguishes itself from sibling tools like fpl_get_fixtures_for_gameweek by focusing on the overall gameweek state rather than fixtures or manager data.

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 says it's 'Essential for determining which gameweek to plan transfers for and understanding the current state of the season,' providing context for use. However, it does not explicitly compare with alternatives or specify when not to use this tool (e.g., when fixture details are needed instead). The guidance is implied but not comprehensive.

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