Team page

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety bar is met. The description adds real value beyond that by explaining the returned 'form' field semantics (last three results, W/D/L, newest first, all/home/away) – information no structured field carries. It stops short of describing payload size, pagination or error behavior.

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?

Front-loaded with the payload summary, then usage examples, then field semantics, then sibling routing – a sensible order with little waste. The board-split sentence and the redundant 'optionally transfers' phrase cost it a point.

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 carries the return-shape burden and does so for the non-obvious 'form' field, which is the main ambiguity. A brief note on what the response looks like for futsal teams, or on squad ordering, would close the remaining gap.

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 100% and each parameter (sport, squad, team_id, transfers) is already documented, including the futsal caveat. The description adds only the 'optionally transfers' note, which duplicates the schema default of false, so this is baseline territory.

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 a specific verb and resource ('Get a football team's page') and enumerates the payload (name, followers, recent form, squad by position, optional transfers). This clearly separates it from v3_team_matches, v3_team_players and v3_news, which are named explicitly.

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?

Gives concrete trigger phrases ('who plays for Esteghlal', 'latest signings') and routes the agent away to v3_team_matches for matches and v3_news with scope="team" for news. It does not say what to do when the team_id is unknown, though the schema points to v3_search/v3_standings.

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