departure_platform

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the key behavioral nuance: before the live platform is announced, the booked timetable platform is returned and flagged as 'booked'. This is valuable context beyond a simple 'get platform' statement.

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 brief and front-loads the core purpose, followed by an important timing caveat. It is slightly awkwardly phrased ('Which platform one train leaves from') but remains efficient and free of unnecessary filler.

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 that an output schema exists and the parameter schema is fully described, the description covers the essential behavioral context. It explains the live-versus-booked distinction, which is the main nuance an agent needs. It could mention how the train is identified via station and time, but the schema already provides this.

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 the schema already documents all three parameters. The description does not add much parameter-level detail beyond what the schema provides, which is acceptable given the high coverage.

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 tool's purpose: returning the platform from which a single train departs. It also distinguishes the live vs booked platform behavior, which helps differentiate it from sibling tools like platform_departures, though it does not explicitly name any sibling.

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 provides useful context about when live platforms become available (~10 minutes before departure) and that booked platforms are returned otherwise. However, it does not explicitly state when to use this tool versus alternatives such as platform_departures or live_departures, leaving some inference to the agent.

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