TV schedule

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

Annotations already declare read-only, idempotent, open-world behavior, so the description's added value is the 'next days' time window and the note that stream links open externally on anten.ir — useful operational context. It stops short of describing pagination or what happens when max_items is capped, but nothing essential is omitted.

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 the core capability in the first sentence, followed by example intents and the routing note. Slightly busy with the parenthetical Persian gloss and the anten.ir aside, but every sentence carries actionable information.

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 usefully explains what comes back (start times, stream links, match_id linkage). Combined with complete parameter documentation and annotations, an agent has enough to call and interpret the tool, though response shape is described only loosely.

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 100%, so both parameters are already fully documented in the schema, giving a baseline of 3. The description adds only an implicit hint that query text is Persian (already stated in the schema) and does not elaborate on max_items behavior.

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?

Names a specific verb and resource — 'live broadcast schedule of sports matches' — plus the key payload (start times, stream links). This clearly separates it from sibling tools like v3_scores (results) and v3_match (match data).

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 concrete example intents ('which matches are on live today', 'when is the Liverpool game broadcast') and an explicit hand-off rule: match_id goes to v3_match. It does not explicitly say when NOT to use it versus v3_scores or v3_news, but the context is clear enough to route on.

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