sm_rounds

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

With no annotations available, the description carries the full burden for behavioral disclosure. It only states the high-level purpose without describing return format, pagination, error handling, or side effects. The mode mention hints at behavior but doesn't disclose what each mode actually returns.

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 exceptionally concise with two sentences, front-loading the primary purpose and immediately adding a relevant workflow note. No words are wasted, and the structure helps quickly orient the agent.

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?

Given four parameters, no annotations, and no output schema, this description is too sparse. It leaves major gaps: what 'all' mode does, how include works, the interplay between id/seasonId and modes, and what the response shape is. Reliable invocation would require additional context.

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 only 25%, so the description must clarify parameter meaning. It explains the mode values (though omitting 'all') and implies the id parameter's role for standings, but it does not clarify seasonId or include semantics. The incomplete explanation falls short of compensating for the sparse 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 identifies the tool's action ('Get round information') and differentiates among modes ('by_season', 'by_id'), which helps distinguish it from sibling tools like standings. However, it omits the 'all' mode defined in the schema, making the purpose slightly incomplete.

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?

The description provides a contextual hint that round IDs are needed for standings by round, implying a common use case. But it doesn't explicitly state when to use this tool versus alternatives or mention the 'all' mode, leaving usage guidance implicit rather than explicit.

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