aliases_list

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. 'List all aliases' clearly indicates a read-only operation, but it does not mention return format, error handling, or edge cases. The description adds no details beyond the basic purpose.

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 two short sentences, front-loaded with the core purpose and followed by the key feature support. Every word earns its place, with no redundancy or fluff.

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 simple list tool with 5 documented parameters, the description conveys the essential purpose, pagination, and search support. It does not have an output schema, but the return value is implicitly a list of aliases. The description is adequate for the tool's complexity, though it could mention the domain-scoped nature more explicitly.

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 baseline is 3. The description mentions pagination and search, which map to page, limit, and query parameters, but it adds no additional meaning beyond what the schema already documents. No compensation needed.

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 specific resource 'all aliases for a domain', clearly distinguishing it from sibling tools like alias_get (single alias) and alias_create/update/delete. It also highlights pagination and search capabilities, which further define the tool's scope.

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 the tool is for listing all aliases for a domain, but it does not explicitly state when to use it versus alternatives (e.g., alias_get for a single alias). There is no when-not guidance or comparison with sibling list tools.

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