list_quotes

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'List quotes' and mentions filtering, but does not disclose whether it is read-only, how pagination works, what max_items does, response limits, or any error behaviors. This is a minimal description with no added behavioral context.

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?

The description is a single, concise sentence that front-loads the main action ('List quotes') and adds one key detail about filtering. It wastes no words.

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?

The tool is simple but the description omits important context: it does not mention the max_items parameter at all, nor does it clarify whether property_ids is a required filter or how the result set is constrained. Although an output schema exists, the description alone is insufficient for an agent to invoke the tool correctly in many situations.

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%, so the description must compensate. It adds the comma-separated format for property_ids, but does not explain the meaning or usage of max_items. The description leaves one of two parameters completely undocumented.

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 a specific verb ('List') and resource ('quotes'), and mentions an optional filter. It distinguishes from sibling tools like list_bookings or list_owners by naming quotes, but does not explicitly contrast with them.

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 implies when to use this tool (to list quotes, optionally filtered by property IDs), but provides no explicit guidance on when not to use it or which alternatives might be preferable. It lacks a direct comparison to sibling list tools.

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