list_aliases

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

Annotations already declare readOnlyHint and idempotentHint, so the description's role is lighter. It adds the key behavioral context of optional scoping to a VMR and explains each filter parameter, which is sufficient beyond the annotations.

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 minimal and front-loaded: one sentence for purpose followed by parameter documentation in a bullet-like list. No redundant words, earning its place.

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 5 optional parameters, presence of an output schema, and annotations, the description covers core functionality and all parameters. It does not explain pagination beyond limit/offset or define 'alias', but these are minor omissions for a list tool.

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?

With 0% schema coverage, the description fully documents all 5 parameters: vmr, alias, alias_contains, limit, offset. Each has clear, actionable meaning (e.g., 'VMR id or exact name to filter by' and 'Case-insensitive substring match').

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 'List conference aliases, optionally scoped to one VMR' clearly states the action (list) and resource (conference aliases), with optional filtering. It distinguishes from sibling tools like list_registration_aliases by specifying 'conference' aliases.

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?

No explicit guidance on when to use this tool versus alternatives. It does not mention when to omit scope or how to choose between exact match vs substring search. The agent must infer usage from parameter descriptions.

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