get_my_fixtures

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

Without annotations, the description fully details output fields, sorting, and a caveat about danishBroadcast being best-effort. Lacks info on error handling or permissions, but adequate for a read operation.

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?

Concise at ~100 words, front-loaded with main action, structured logically with no unnecessary sentences.

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?

Covers all essential aspects: what, who, configuration, output, sorting, usage tip, caveat. Lacks explicit differentiation from siblings but is sufficient for its simple scope.

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?

With 100% schema coverage, the description adds no extra semantics beyond the schema's parameter definition. Baseline score applies.

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?

Description clearly states verb 'get', resource 'upcoming fixtures', and scope 'for all followed football teams within the next N days'. It lists default teams and distinguishes itself from siblings as the primary daily check tool.

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?

Explicitly indicates this is the primary tool for ARIA's daily check and suggests calling once to see if any team plays soon. Does not explicitly state when to avoid, but context is clear.

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