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

With no annotations provided, the description carries the full burden. It discloses what is produced (captain, VC, top-5 options) and that it operates on the manager's current squad, which is useful. It does not say whether it is a read-only lookup, whether team_id must be the authenticated manager's team, or how fresh the data is.

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?

A single compact fragment with no filler, and the key scoping detail (next gameweek, manager's current squad) is front-loaded. It would be stronger as a complete sentence, but nothing is wasted.

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 and no annotations, the description partially compensates by enumerating the returns (captain, VC, top-5 options). It leaves the sole parameter unexplained and gives no context on data source or staleness, so it is only minimally complete for a one-parameter lookup tool.

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% and there is one required parameter (team_id) that the description never explains. The phrase 'a manager's current squad' hints that team_id identifies the manager, but nothing clarifies format, source, or whether it must be the caller's own team.

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 names a concrete resource and scope — captain, vice-captain, and top-5 captaincy options from a manager's current squad for the next gameweek. An agent can tell this apart from siblings like compare_players or suggest_transfers, though it is written as a noun fragment rather than an explicit verb+resource statement.

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 statement of when to use this tool versus alternatives such as compare_players, model_report, or predict_points. The 'next gameweek' scoping is implied but no condition, prerequisite, or exclusion is given.

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