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

readOnlyHint=true already establishes this is a safe read, so the bar is lower. The description adds that the ETA is 'live' and sourced 'from the routes sent to drivers', which is useful freshness context, but says nothing about behavior when the order is unknown or not yet scheduled.

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 returned content in one tight sentence, zero fluff. The trailing 'OptimoRoute: GET /get_scheduling_info.' restates the endpoint and is minor waste, but does not bury the substance.

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?

No output schema exists, so the description must describe returns, and it does so concretely (driver/vehicle, stop number, time, live ETA) including the negative case of the order not being scheduled. Enough for a two-optional-parameter read tool whose safety profile is covered by annotations.

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 coverage is 100% and both parameters are already documented there, so the schema carries the load. 'Give orderNo or id' usefully signals that either identifier works (consistent with zero required params), but adds no format or precedence detail beyond the schema.

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?

States a specific retrieval (scheduling info for one order) and enumerates exactly what comes back: scheduled status, driver/vehicle, stop number, time, and live ETA. That enumeration distinguishes it from siblings like get_dispatch_status, get_planning_status, and get_routes without needing to name them.

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 frames the use case as the question an agent would ask ('Is this order scheduled...') and tells it to supply orderNo or id, so usage is implied but never contrasted with alternatives such as get_planning_status or get_dispatch_status. No when-not-to-use guidance.

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