get_manager_info

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

With no annotations, the description carries full burden. It fails to mention if the operation is read-only, requires authentication, or what happens on invalid team_id. Only states returns are 'Manager info with leagues and performance stats' without behavioral details.

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?

Short and structured with Args/Returns sections. Every sentence adds value, though the description could be slightly more concise by removing the argument template repetition.

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?

Lacks depth: no output schema, no error handling, no return field details. For a tool returning leagues and stats, the description is incomplete given the absence of schema richness and the presence of sibling tools.

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 description coverage is 0%, but the description explains the parameter 'team_id' clearly as 'FPL team ID (defaults to authenticated user)', adding meaning beyond the schema's title. Could be improved with more precise format guidance.

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?

States 'Get detailed information about an FPL manager' with specific mention of 'leagues and performance stats', making the purpose clear. However, it doesn't explicitly differentiate from sibling tools like 'get_manager' or 'get_my_team'.

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?

Provides no guidance on when to use this tool versus alternatives. Mentions the default for team_id but offers no exclusions or context for selection among sibling tools.

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