sm_standings

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

With no annotations provided, the description must carry the full transparency burden. It does not disclose conditional parameter requirements (e.g., live mode needs leagueId, by_round likely needs roundId) or describe response characteristics, leaving the agent uncertain about correct invocation.

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 description is two sentences with the core purpose front-loaded. The modes are listed efficiently, and only the phrase 'Essential for form analysis' is mildly non-operational, but overall it is concise and well-structured.

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?

Without an output schema or annotations, the description should compensate by clarifying per-mode required parameters and return value shape. It does neither, leaving significant gaps for an agent trying to invoke the tool correctly.

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 coverage is high (80%), so the baseline is 3. The description adds minimal value by noting 'live standings by league', which hints at the leagueId parameter, but does not explain other parameters beyond the schema.

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 states 'Get league standings / tables', which is a specific verb+resource. It lists the three modes, further clarifying scope. This distinguishes it from sibling tools like sm_fixtures or sm_topscorers.

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?

'Essential for form analysis' provides a clear when-to-use context. The mode list implies different invocation scenarios, though no alternatives are explicitly named or excluded.

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