env_group_delete

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

The description goes beyond the simple deletion action by stating 'Los entornos del grupo quedan como globales' (The group's environments become global), which is a key behavioral consequence. No annotations are provided, so the description carries full burden, and it delivers relevant side-effect information.

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, well-structured sentence that immediately states the action and the side effect. Every part adds value; no redundancy.

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 delete tool with one parameter and no output schema, the description adequately covers the primary action and its main consequence. It could mention if the group must be empty or if the operation is reversible, but the current information is sufficient for basic use.

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 one parameter described ('Nombre del grupo a eliminar'). The description adds no further meaning to the parameter beyond what the schema provides, meeting the baseline expectation for high coverage.

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?

Description clearly states 'Elimina un grupo' (Deletes a group), a specific verb and resource. It distinguishes from sibling tools like env_group_create, env_group_list, env_group_add_scope, which have different actions.

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 implies usage by stating the deletion and its effect on environments. While no explicit alternatives or exclusions are given, the context is clear that this tool is for deleting a group, and the side effect is mentioned.

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