get_team_fixtures

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

No annotations provided, so description carries full burden. It describes the output structure (fixture entries vs result entries) and notes that 'danishBroadcast' is best-effort, with verification links. Could mention rate limits or error handling, but overall informative for a read tool.

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 purpose and core parameters. The final note on broadcast verification is useful context but slightly lengthens the description. Generally efficient with no redundancy.

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 adequately explains return types (fixture vs result entries). Covers behavior of all parameters and provides verification guidance. Lacks error handling or edge case info, but sufficient for typical use.

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 100% with parameter descriptions. Description adds value by explaining the interaction between 'days' and 'last' (ignored when last is set) and describing the output format, which goes beyond schema definitions.

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?

Clearly states it gets upcoming fixtures or recent results for a football team by name or ID. Differentiates from siblings like get_my_fixtures (user-specific) and live_now (current live) by its team-specific focus and date/result modes.

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?

Provides explicit guidance on using the 'last' parameter to switch from fixtures to results. Does not directly compare to sibling tools or state when not to use, but the description's clarity on functionality implicitly guides appropriate use.

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