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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the underlying endpoint (GET /api/v3.3/orders) and the domain meaning of the returned payload, but says nothing about pagination, result limits, or ordering of results, which matter for a list endpoint.

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-loads the resource definition, then the filtering rule, then the endpoint reference. No filler, though the raw endpoint citation earns slightly less than the semantic content around it.

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 read-only list tool with no output schema, the description supplies the domain meaning of an 'order' and the mandatory filter rule, which is enough to invoke it correctly. Missing pagination/shape hints keeps it from being fully complete.

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% and each parameter is documented in the schema (lead_uid, guest_uid, property_uid, updated_since with format example). The description corroborates the filter set but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 (list orders) and goes further by defining what an order actually is — 'the money side of a booking: rent, fees, services, adjustments, taxes, channel commission and total'. That framing lets an agent distinguish it from the other hostfully_list_* tools on semantic grounds rather than name alone.

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?

Gives explicit filter context and a hard usage constraint — 'at least one is required' among lead/property/guest/update time — which is essential to call it correctly. It stops short of naming alternatives (e.g. when to use search_leads or get_lead instead), so no when-not guidance.

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