Get My Squad

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

No annotations are provided, so the description carries the full behavioral burden. It lists returned data but does not explain auth requirements, pagination, default behavior when league_id is omitted, or whether the result is scoped to the current league.

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 single sentence is front-loaded and has no wasted words, listing the key returned fields efficiently. It could be slightly clearer with an explicit verb, but it is appropriately concise.

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?

Although an output schema exists, the description does not resolve the main ambiguity around the optional league_id parameter. With no annotations and no usage guidance, the definition is underspecified for correct invocation beyond a trivial no-argument call.

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 schema has one optional parameter, league_id, with 0% description coverage, and the description never mentions it. The agent receives no explanation of whether league_id filters the squad, defaults to a current league, or is required in practice.

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 identifies the resource as the user's full squad and enumerates the contents returned: market value, trend, points, status and position. It distinguishes 'your' squad from get_manager_squad implicitly, though it does not explicitly route away from siblings such as get_my_lineup or get_manager_squad.

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?

There is no guidance on when to use this tool versus alternatives like get_my_lineup, get_manager_squad, or get_league_overview. The intended use is implied only by the phrase 'Your full squad'.

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