Get environment delete blast radius

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

The description claims a read-only GET operation, but annotations set destructiveHint=true, creating a contradiction. No additional behavioral context is provided, such as whether the operation might incur costs or have side effects.

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 very short but under-specifies important details. It merely repeats the title and adds API path/auth info, leaving out usage context and parameter guidance.

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?

Despite having an output schema, the description does not explain what the blast radius result contains. For a potentially destructive assessment tool, more context is needed to ensure proper interpretation.

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?

The single parameter 'path.id' (string) has 0% schema coverage, and the description adds no meaning about its format, expectations, or role in identifying the environment.

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 name and description clearly state the purpose: retrieving the delete blast radius of an environment. The HTTP method and path are provided, making it distinct from sibling tools like pc_get_environments_by_id or pc_delete_environments_by_id.

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 does not specify when to use this tool versus alternatives. It lacks guidance on prerequisites, such as needing to first call pc_get_environments_by_id, or when to consult before performing a delete.

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