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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds genuinely non-redundant facts: the call is anonymous, destination references carry quote_required=false and procurement_allowed=false, and unknown payable amounts stay null rather than guessed. That is substantive behavioral context beyond the annotations, though it omits pagination and result-shape 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?

Front-loaded with the core action and each following sentence adds a distinct constraint (destination refs, negative scope, null semantics) with no filler. Density of domain jargon ('quote_required=false') is slightly opaque but still compact and purposeful.

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?

With no output schema, the description does sketch the two result kinds, which is valuable. But for a 4-parameter, 0%-documented discovery tool it leaves an agent without paging behavior, query semantics, or hub selection rules — adequate but with clear gaps for correct invocation.

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 0% across four parameters (limit, query, cursor, hub_id), and the description explains none of them. 'six-hub' faintly implies hub_id refers to one of six fixed hubs, but there is no guidance on query matching, cursor/limit paging semantics, or valid hub values, so the coverage gap is not compensated.

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 verb+resource ('Discover published six-hub local-service ideas') and immediately delimits a second result type ('separately labelled destination references'). It distinguishes itself from query siblings like search_flights/search_hotels by naming the domain (local services) and the anonymity trait, though it does not name a sibling explicitly.

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 effectively says what the tool is NOT (not inventory, not a live quote, not a booking) and clarifies that destination references are reading/comparison only, which helps rule out mis-invocation. However, it never states when to prefer this over evuun_create_service_inquiry or evuun_prepare_service_inquiry — the natural next step after discovering isn't routed.

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