List eggs

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

Annotations already cover read-only and non-destructive behavior. The description adds transparency about response content, noting that summary mode drops install scripts and upstream repository copies, and that full details require a single egg request. It does not elaborate on pagination or rate limits, but those are not contradicted by 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 compact and well-organized, leading with the core purpose and then adding usage nuances. It contains no unnecessary words and is easy to parse.

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 that no output schema is provided, the description gives useful context about response content (summary vs full) and required permissions. It could mention pagination behavior, but the overall context is sufficient for an agent to call the tool correctly.

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 coverage is 100% with each parameter described, so the baseline is 3. The description adds a bit of semantic nuance by explaining the effect of omitting vs providing nest and the detail trade-off, but it mostly relies on the schema for parameter meaning.

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 tool's purpose: 'List eggs (server templates).' It also clarifies the distinction between listing all eggs or filtering by nest, which helps differentiate it from sibling tools like get_egg.

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 gives explicit usage guidance: omit nest for all eggs grouped by nest, or pass a nest UUID to filter. It also explains when to use detail 'full' vs the default summary, and mentions the required eggs.read permission. It does not explicitly name sibling alternatives but implies them.

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