list_agents

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

With no annotations, the description bares full responsibility for behavioral disclosure. It fails to mention that the tool is paginated (as evidenced by page and pageSize parameters) and that keyword filters results. The phrase 'all available' is misleading given pagination. No info on response structure or authentication is provided.

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 zero fluff. It conveys the essential purpose immediately and is appropriately sized.

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 description omits critical operational details like pagination behavior, keyword filtering semantics, and return values. Given the absence of an output schema and annotations, this minimal description is insufficient for an agent to fully understand the tool's behavior.

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 100%, so the parameters (page, keyword, pageSize) are already documented. The tool description adds no extra meaning beyond what the schema provides, earning the baseline score of 3.

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 states a specific verb ('List') and resource ('available AI agents'), clearly distinguishing it from sibling tools like get_agent or list_conversations. The scope is also explicit with 'in DreamingAI', making the purpose unambiguous.

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 usage for listing all agents, but does not explicitly mention alternatives such as get_agent for a single agent, nor does it explain when filtering via keyword would be appropriate. Context is clear but there are no exclusions or explicit alternative guidance.

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