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

No annotations are provided, so the description must disclose behavioral traits. It indicates 'listing summaries' but doesn't specify pagination, sorting, rate limits, authentication needs, or whether results are limited. As a read-only tool, this is basic but incomplete.

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?

One sentence, front-loaded with the primary action and resource. No wasted words. Could be more structured with bullet points, but it's sufficiently concise.

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?

Given no output schema, no annotations, and low schema coverage, the description should provide more context. It lacks details on result format, pagination, default behavior (e.g., without filters), and how it differs from 'get_listing' or 'search_timeshares'. Incomplete for an effective interaction.

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 coverage is 0%, so the description must compensate. It adds context by saying 'filterable by state or brand', which maps to two parameters. However, it does not explain the 'limit' parameter or provide defaults/enums. Partial compensation.

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 clearly states the verb (list), resource (resorts with summaries), and filtering options (state or brand). It distinguishes from sibling tools like 'get_resort' (single item) and 'search_timeshares' (different domain).

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?

No guidance on when to use this tool versus alternatives. No exclusions, prerequisites, or when-not scenarios mentioned. The description only mentions filtering but doesn't clarify when to use this over, e.g., 'get_resort' for detailed info.

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