get_team

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

No annotations exist, and the description does not mention authentication, rate limits, error handling, or what happens with invalid inputs. For a read operation, it lacks basic behavioral context beyond the return type.

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?

Description is relatively short and front-loaded with the action and resource. The docstring format is slightly verbose but overall efficient for the information conveyed.

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?

With no output schema, the description states it returns 'detailed team information including player details, captain, and value', but lacks specifics on the structure or fields. Given the tool's moderate complexity (2 params), this is adequate but not comprehensive.

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?

Description adds meaning to both parameters: 'team_id' is labeled 'FPL team ID (required)' and 'gameweek' is 'Gameweek number (defaults to current gameweek)'. This compensates for 0% schema coverage by explaining purpose and default behavior.

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?

Clear verb ('Get') and resource ('any team's players, captain, and other details') with specific scope (for a gameweek). Distinguishes from siblings like 'get_my_team' (own team) and 'get_manager' (manager info).

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?

Describes what the tool does but provides no explicit guidance on when to use it vs alternatives (e.g., 'get_my_team', 'get_manager'). Usage context is implied but not stated.

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