list_ai_agents

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds no further behavioral context such as pagination behavior, ordering, or whether all agents (including archived) are returned. With annotations, this is adequate but lacks additional useful detail.

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 succinct sentence ('List AI agent definitions') that conveys the core purpose with zero wasted words. It is appropriately sized 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 low tool complexity, full schema coverage, and annotations that signal safe read-only behavior, the description is almost complete. It lacks explicit mention of what the response contains, but the phrase 'AI agent definitions' implies a list of definitions. Minor gap: no mention of default pagination or scope (e.g., includes inactive agents), but these are covered by the schema parameters.

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%, with both 'limit' and 'active' fully documented in the input schema. The description adds no extra parameter context, but the baseline of 3 applies because the schema already handles parameter semantics.

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 resource ('AI agent definitions'), clearly distinguishing it from sibling tools like get_ai_agent (singular retrieval) and create_ai_agent (creation). It unambiguously states what the tool does.

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 when wanting to list all AI agent definitions, but provides no explicit guidance on when to choose this tool over alternatives like get_ai_agent or create_ai_agent. No exclusions or alternative recommendations are mentioned, leaving the context to be inferred from sibling names.

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