create_egg_variable

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

Annotations already indicate this is a destructive operation (destructiveHint: true) and has open-world characteristics (openWorldHint: true). The description adds valuable context beyond annotations by specifying it's an 'admin action' and requires specific API key authentication, which helps the agent understand permission requirements not captured in 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 efficiently structured in three sentences: purpose statement, parameter guidance, and authentication requirement. Each sentence adds distinct value with zero wasted words, making it easy to parse and understand quickly.

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 destructive admin tool with 9 required parameters and no output schema, the description provides good context about prerequisites, authentication, and parameter syntax. However, it doesn't mention potential side effects, error conditions, or what happens on success - gaps that could be important for a destructive operation.

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 100% schema description coverage, the input schema already documents all 9 parameters thoroughly. The description adds minimal parameter-specific information - only clarifying the syntax for the 'rules' field ('uses Laravel validation syntax'). This meets the baseline expectation when schema coverage is complete.

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 action ('Add a new environment variable'), the target resource ('to an egg'), and the required permission level ('admin action'). It distinguishes from siblings like 'update_egg_variable' and 'delete_egg_variable' by specifying creation of a new variable rather than modification or deletion.

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 provides clear context about prerequisites ('Use list_nests and list_eggs to find the nest_id and egg_id') and authentication requirements ('Requires Application API key'). However, it doesn't explicitly state when NOT to use this tool or mention alternatives like 'update_egg_variable' for existing variables.

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