ai_list_quick_responses

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 merely states 'List quick responses' without mentioning pagination, sorting, response format, or whether it returns responses from all knowledge bases or only the specified one.

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 extremely concise at three words, with no wasted language. However, it is under-specified, lacking important context about scope and parameters. It is concise but not appropriately sized for the tool's complexity.

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 tool with two parameters (one required) and a sibling search tool, the description is too sparse. It doesn't mention that quick responses are scoped to a knowledge base, nor does it clarify the difference between listing and searching. The output schema exists, so return values aren't needed, but the description still feels incomplete.

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 no explanation for 'knowledge_base_id' or 'max_results', although the parameter names and the default value are relatively self-explanatory. The description provides zero added meaning over the schema.

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 'List quick responses' uses a specific verb (List) and resource (quick responses), clearly indicating a read operation. However, it does not differentiate from the sibling tool ai_search_quick_responses, nor does it mention the knowledge base scoping implied by the required parameter.

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 provides no guidance on when to use this tool versus ai_search_quick_responses or other list tools. It lacks any indication that this lists quick responses within a specific knowledge base, which is implied by the schema but not stated.

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