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

readOnlyHint=true is consistent with a static-facts lookup, so no contradiction. The description adds the content scope (which fact categories are covered) but nothing beyond that — no note that the data is static/cacheable or what the response looks like. Adequate given annotations carry the safety signal.

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?

Two short sentences, front-loaded with the resource and its contents, with the disambiguating note last. No filler or repetition of the name.

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 zero-parameter, read-only info lookup with no output schema, the description covers what facts are returned and what the business is. The only gap is that it never frames the result as a fixed business profile versus live data, but nothing an agent needs to invoke it correctly 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 takes zero parameters, which is the baseline-4 case per the rubric. Nothing in the description needs to explain inputs, and it correctly implies the call is context-free.

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 resource (CGC Airport Transfers business facts) and enumerates the categories returned: contact, hours, fleet, inclusions, policies. The clarifying line distinguishes the business model from taxi/rideshare, but it differentiates the service rather than this tool from its action siblings (get_quote, request_booking), so it stops short of a 5.

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?

Usage is only implied: an agent can infer this is the static-information lookup versus the transactional siblings, but no sentence says when to call it or when to prefer check_availability or get_quote instead. The 'not a taxi or rideshare' line is scope clarification about the business, not tool-selection guidance.

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