live_now

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

Discloses premium vs free tier behavior (structured unavailable notice), and notes that danishBroadcast is a best-effort hint. No annotations exist, so description fully covers behavioral traits.

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?

Two concise sentences plus a helpful note, front-loaded with core action. No wasted words.

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?

Explains return values for both premium and free tiers, despite no output schema. Covers behavioral caveat about danishBroadcast. Complete for a zero-parameter tool.

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?

No parameters in schema, description does not need to add parameter info. Baseline of 4 applies as it adds meaning about the tool's function beyond the empty 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?

Description clearly states it checks if any followed football team is currently playing, with a specific verb and resource. It distinguishes from sibling tools like get_my_fixtures (fixtures) and get_results (results) by focusing on live status.

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?

Describes when to use (current live status) but does not explicitly exclude alternatives. Provides context on premium vs free key limitations.

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