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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that the tool returns factual reference information rather than performing actions, but it does not state freshness, source reliability, or whether the content is static.

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?

A single front-loaded sentence names the resource and then lists the covered topics. There is no redundant or filler wording.

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 simple no-parameter reference tool with no output schema, listing the topics is enough for an agent to know what information is available. Completeness would improve with a note on freshness or a clearer distinction from transactional siblings, but no essential calling information is missing.

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 parameter semantics are not applicable and the baseline is 4. The description correctly implies a no-argument informational call.

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 resource (OrangeRide facts) and enumerates the covered topics: area, booking notice, payment, Gatwick meeting points, flight tracking, and contact details. It is clear enough to distinguish a general reference tool from transactional siblings like request_booking or confirm_booking, though the verb 'facts about' is somewhat broad.

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 enumerated topics imply when to use the tool—when an agent needs general service information—but there is no explicit when-to-use or when-not-to-use guidance. Alternatives such as check_flight for flight status or get_quote for pricing are not mentioned, leaving the agent to infer routing.

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