get_cancelled_trains

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

With no annotations, the description carries the full behavioral disclosure burden. It usefully states that results are real-time and limited to today's cancellations, including fully and partially cancelled categories, but it does not describe permissions, response structure, rate limits, or empty-result 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 a single, front-loaded sentence with no redundant or filler text. Every part contributes to clarifying the resource, freshness, time scope, and cancellation categories.

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?

For a no-parameter, no-output-schema tool, the description gives enough context to understand what the tool returns: a real-time list of today's cancelled trains, split into fully and partially cancelled categories. It could be stronger with explicit usage guidance or return-format detail, but the low complexity makes the current description largely adequate.

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?

The tool has zero parameters, so there is no parameter semantics burden. The description correctly avoids discussing nonexistent inputs, and the empty input schema is consistent with the description.

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 states a specific verb and resource: get today's cancelled Indian Railways trains. It also scopes the data to real-time, today-only, and distinguishes fully cancelled from partially cancelled trains. The uniqueness of the resource makes it clearly distinguishable from sibling tools like get_live_running_status or check_pnr.

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 the tool is for users asking about today's train cancellations, but it does not explicitly state when to use it versus alternatives. No exclusions or related-tool routing guidance is provided, so the agent must infer usage from the purpose statement.

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