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

Annotations already declare destructiveHint=true, but the description adds meaningful context beyond the structured safety hints: it discloses the cascade effect (deployments are deleted) and the approval gate. It does not cover irreversibility or permissions fully, but it earns credit for exposing destruction scope and auth workflow.

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?

Two short sentences, front-loaded with the core action and immediately followed by the critical prerequisite. No filler, though the phrase 'BEON PASS' is unexplained and the description is very sparse given the tool's complexity.

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?

With no output schema and 0% schema parameter descriptions, the description should compensate by explaining how to supply 'id', 'approval_id', and the several beon_* parameters. It mentions approval in passing but does not map it to 'approval_id' or clarify the other required context fields, leaving significant gaps for a destructive, multi-parameter 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 0% across 8 parameters, including required 'id' and UI-related fields like 'approval_id' and 'beon_context'. The description does not explain any parameter's meaning, format, or role, leaving the agent without semantic guidance.

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 (Delete) and resource (environment), and clarifies that deployments are also removed. It does not explicitly differentiate from siblings like railway_delete_project or railway_delete_service, but the resource is unambiguous.

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?

Only mentions the approval prerequisite ('Requires exact user approval in BEON PASS'). It gives no guidance on when to choose this tool versus alternatives, nor any exclusions or typical context for deletion.

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