List quotes

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

No annotations are provided, so the description carries the full burden. It reveals only that the result is paginated, which is a minor behavioral trait. It does not disclose return format, authentication requirements, side effects, ordering, or any constraints beyond pagination. For a list operation with no annotation coverage, this is insufficient.

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, front-loaded sentence with no filler words. It is appropriately concise for a simple list operation, though it borders on under-specification. For a tool with only a name and title, it conveys the core purpose efficiently.

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 four optional parameters with no descriptions, the description is far from complete. It does not explain the response structure (beyond pagination), how filters work, or any constraints like the pageSize maximum (even though the schema includes max: 200). An agent would not have enough context to call this tool correctly without additional inference.

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?

The schema has 0% description coverage, and the description does not mention any of the four parameters (search, status, pageSize, pageNumber). It fails to explain what these parameters mean or how they affect results. Since the description provides no semantic value beyond the parameter names, it does not compensate for the lack of schema descriptions.

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 action ('List') and the resource ('price quotes'), and adds the pagination detail. It is specific enough to distinguish from other list tools in the sibling set like list_leads or list_cases, though it does not explicitly contrast with get_quote. The verb and object are clear and not a tautology.

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 is provided on when to use this tool versus alternatives (e.g., get_quote for a single quote, or list_invoices for a different resource). There is no mention of scenarios where this tool is appropriate or when another should be chosen. The description offers no context on filtering or typical use cases.

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