next_fixture

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

No annotations are provided, so the description must fully disclose behavioral traits. It does not specify what happens at boundaries (e.g., wrap-around, no effect) or how selection state changes. This lack of detail leaves the agent uncertain about side effects.

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 a single, clear sentence. It contains no redundant or extraneous words. Every word contributes to understanding the function, making it highly efficient.

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?

The tool is simple but lacks explanation of boundary behavior or prerequisites. Given the presence of an output schema (not shown), the description is adequate for basic use but incomplete for robust understanding.

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 input schema has zero parameters, so schema coverage is 100%. The description adds no parameter information, but none is needed. It correctly states the action without requiring parameters, meeting the baseline for a no-parameter tool.

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 action ('Step to the next fixture') and the resource ('in the current selection'). The verb 'Step to' and noun 'fixture' are specific and unambiguous. The purpose is immediately understandable and distinguishes from sibling 'previous_fixture'.

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?

No explicit guidance on when to use this tool versus alternatives like 'previous_fixture' or 'locate_fixtures'. Usage context is implied but not detailed, e.g., no mention of behavior when at the last fixture or with an empty selection.

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