get_schedule

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

Adds behavioral detail: score returned only if match is played. Annotations already provide readOnlyHint, idempotentHint, etc. No contradiction.

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: four sentences covering purpose, return details, prerequisite, and args. Front-loaded with key action. No redundant text.

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 returns, prerequisite, and parameter sources. Output schema exists, so return structure is externally defined. Lacks error or pagination info, but acceptable.

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 0% schema description coverage, description explains event_id as 'Numeric event ID (e.g. 3933)' and flight_id's source. Adds value beyond schema types.

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 'all matches for a flight', and specifies returned fields (date, time, venue, teams, score). Distinguishes from siblings like get_match (single match) and get_team_schedule (team-specific).

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 prerequisite: 'Get the flight ID from get_event_overview.' Lacks explicit when-not-to-use or comparison with alternatives like get_results, but the prerequisite is useful context.

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