list_aliases

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

The description indicates a read-only 'List' operation and lists the returned fields, but it does not mention potential pagination, ordering, errors, or other behavioral caveats. With no annotations provided, more behavioral detail would strengthen transparency.

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 concise sentence that efficiently communicates the action, scope, and return fields with no unnecessary words or repetition.

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 parameterless list operation, the description adequately covers the purpose and the returned fields. It lacks an explicit output schema but compensates by naming all returned attributes, so an agent can understand what to expect.

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, so there are no parameter semantics to document. The baseline score of 4 applies because no parameter description is 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 clearly states the verb 'List', the resource 'email aliases', and the scope 'all on the authenticated EmailAlias account'. It distinguishes itself from sibling tools by focusing specifically on aliases rather than domains, destinations, or logs.

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 purpose implies when to use the tool (when needing a list of aliases), but it does not explicitly mention alternative tools or conditions for choosing this one over siblings like list_available_domains or list_destinations.

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