ai_list_assistants

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

With no annotations, the description must fully convey behavioral traits. The verb 'List' implies a read-only operation, but the description does not explicitly state that it has no side effects, nor does it mention pagination, limits, or result ordering. This lack of additional behavioral context gives little beyond the operation itself.

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, clear sentence that front-loads the action and resource. It contains no filler words, making it appropriately concise for the tool's simplicity.

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 the tool has no parameters, an output schema exists, and the action is straightforward, the description is mostly sufficient. The agent can invoke the tool without ambiguity, though it does not clarify the scope of 'Amazon Q assistants' or whether all assistants are returned. The output schema likely covers return structure, so this is acceptable.

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 tool has zero parameters, and the input schema confirms an empty object. The description does not need to explain parameter meaning because none exist. This matches the baseline for 0-parameter tools, scoring 4.

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 uses a specific verb ('List') and a clear resource ('Amazon Q assistants'), which accurately conveys the tool's function. However, it does not explicitly distinguish this tool from sibling list tools like ai_list_knowledge_bases or ai_list_quick_responses, so it falls short of a 5.

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 alternatives. It lacks any context about prerequisites, exclusions, or scenarios where this tool is preferred over similar list tools, offering no usage direction beyond the literal action.

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