get_departure_monitor

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

No annotations are provided, so the description carries the full burden. It mentions using 'direct HTTP requests to the Transport NSW API', which hints at external API calls, but doesn't disclose critical behavioral traits like error handling, rate limits, authentication needs, or what 'simplified list' means in the Returns section. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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?

The description is well-structured with a clear purpose statement upfront, followed by an Args section with bullet-point details and a Returns section. It's appropriately sized for a 5-parameter tool, though the 'This function uses direct HTTP requests...' sentence could be integrated more tightly or omitted if redundant with context.

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?

Given no annotations and no output schema, the description provides good parameter semantics and a basic return type ('Simplified list of departure information'), but lacks details on output structure, error cases, or API constraints. For a tool with moderate complexity (5 parameters, external API), it's adequate but has clear gaps in behavioral context.

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 0%, so the description must compensate. It provides detailed semantics for all 5 parameters, including formats (e.g., 'DD-MM-YYYY' for date, 'HH:MM' for time), defaults, and a clear enum-like explanation for 'mot_type' with transport mode options. This adds substantial value beyond the bare schema, though it doesn't fully explain all edge cases (e.g., what 'global stop ID' entails).

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?

The description clearly states the specific action ('Get real-time departure monitor information'), the resource ('for a specific stop'), and the source ('from the Trip Planner API'). It distinguishes this tool from sibling tools like 'find_transport_stops' (which likely finds stops) and 'get_transport_alerts' (which gets alerts rather than departures).

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?

The description implies usage by specifying it's for departure information from a stop, but doesn't explicitly state when to use this tool versus alternatives like 'find_transport_stops' or 'get_transport_alerts'. No exclusions or prerequisites are mentioned, leaving the agent to infer context from the tool name and description alone.

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