Delete project machine pool grant

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnly=false, so the safety profile is covered. The description earns credit by adding the blast radius beyond those hints: it revokes machine grants generated through the grant and stops dependent processes, while the pool survives. It omits permissions/auth requirements, but the cascade disclosure is genuinely useful context.

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 sentences, zero filler, with the primary effect front-loaded ahead of the retention and blocker notes. Well-sized for the operation, though slightly more terse than ideal given the missing 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?

For a destructive mutation with annotations covering safety and no output schema, the description supplies the consequential details: what is destroyed, what is preserved, and that no blockers exist. It is close to complete; only permission requirements and parameter meaning are unaddressed.

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 three required string parameters, and the description mentions neither parameter names nor their meaning, formats, or constraints. It fails to compensate for the coverage gap, leaving the agent to infer semantics from parameter names alone.

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 plus resource ('Removes the project's access to the machine pool') and enumerates the cascade effect, and explicitly distinguishes itself from the pool-deletion sibling with 'The pool itself is retained.' An agent can tell this apart from grant_pools_edit and pools_delete without opening a schema.

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 verb 'removes' implies when to use it, and 'there are no dependency blockers' tells the agent no pre-checks are needed. However it never names an alternative (e.g., revoke via grant_pools_edit) or states an explicit when-not condition.

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