delete_egg_variable

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

Annotations provide destructiveHint=true and openWorldHint=true, but the description adds significant context: 'This is permanent and cannot be undone' clarifies the irreversible nature, and 'Requires Application API key' specifies authentication needs. These details go beyond annotations, enriching behavioral understanding without contradiction.

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 front-loaded with the core action, followed by critical warnings and prerequisites in three concise sentences. Each sentence adds value: purpose, permanence warning, and usage guidance, with zero wasted words.

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 tool's destructive nature, annotations cover safety (destructiveHint), and the description adds essential context like permanence and auth requirements. With no output schema, the description doesn't need to explain return values, making it complete for this admin deletion 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?

Schema description coverage is 100%, with each parameter documented (e.g., 'Nest ID that contains the egg'). The description adds no additional parameter semantics beyond referencing 'variable_id' from 'list_egg_variables'. Baseline 3 is appropriate as the schema fully covers parameters.

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 specific action ('Delete an environment variable from an egg') with the resource identified ('egg variable'). It distinguishes from siblings like 'delete_egg' (different resource) and 'update_egg_variable' (different action), providing precise verb+resource differentiation.

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?

Explicit guidance is provided: 'Use list_egg_variables to find the variable_id' indicates a prerequisite step, and 'admin action' plus 'Requires Application API key' specify access requirements. This clearly tells when and how to use this tool versus alternatives like 'list_egg_variables' for discovery.

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