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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description goes further by disclosing the downstream consequence ('can trigger deployment and break applications') and a required approval gate. This is genuine added context beyond the annotations, though it doesn't explain what the approval flow returns or whether the delete is reversible.

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?

Three short sentences, front-loaded with the action before the risk warnings. Every clause earns its place with no repetition of the name or title.

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?

Covers the two critical facts an agent needs (destructive consequence, approval gate), which is important given no output schema. But with 11 parameters undocumented in both schema and description, and no clarification of how approval_id/beon_context are supplied, the definition is not complete for correct invocation.

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 0% across 11 parameters, so the description carries the burden and largely fails it: no parameter is named, and the required approval_id, projectId, environmentId, and name are never mapped to the stated approval requirement. Only an oblique hint ('requires exact user approval') gestures at the approval parameter.

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?

States a specific verb and resource ('Delete a variable'), which is unambiguous and clearly the inverse of the sibling railway_set_variable. However, it does not explicitly name that sibling or the read counterpart (railway_list_variable_names), so differentiation is inferred rather than stated.

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?

Gives one hard precondition ('Requires exact user approval in BEON PASS') but no guidance on when to prefer this over updating a variable in place, nor which scope (environment vs service) to target. Usage context is implied rather than explained.

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