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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the endpoint ('GET /listings') and which fields come back, but says nothing about pagination behavior, result caps, or ordering; the schema carries the next_page/per_page mechanics instead.

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 tight sentences: the first defines the resource and payload, the second enumerates filters, and the endpoint is appended. No filler and the core purpose leads.

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 18 optional params, no output schema, and no annotations gaps, the description does the important extra work of listing returned fields in lieu of an output schema. It falls slightly short by not covering the 'include' expansion option or pagination flow, though the schema documents both.

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%, so the baseline is 3. The description groups the main filter families (text, address, agent, status, price/size, delivery status), which reinforces intent, but it omits the non-obvious 'include' relation-expansion parameter and the bedrooms/bathrooms range filters.

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 ('List') and resource ('property listings of your Aryeo company'), then enumerates the fields returned (address, status, price, bedrooms, delivery status, thumbnails). This clearly separates it from the single-record sibling aryeo_get_listing.

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 filter list ('search text, address, listing agent, status, price/size ranges or delivery status') implies this is the browse/search entry point, but there is no explicit when-not guidance or named alternative such as aryeo_get_listing for a single record or aryeo_get_listing_stats for aggregates.

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