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

The description explicitly labels the action as destructive, notes that it deletes the link after authorization, and warns that provider webhook configuration may be removed. This aligns with the destructiveHint annotation and goes beyond it.

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 compact and information-dense, with no filler. It covers purpose, effect, prerequisites, and required parameters in two sentences.

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?

The description provides sufficient context for a destructive deletion operation, including permissions and side effects. It does not describe the response format, but given the absence of an output schema and the straightforward nature of the action, this is not a significant gap.

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?

Both parameters are fully described in the schema with types and usage guidance. The tool description also references space_id and link_id, and the link_id description adds practical advice to list links first.

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 description clearly states the action: removing an Autopilot repository link from a Space, and distinguishes it from related operations like creating, updating, enabling, or disabling repository links.

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?

Explicitly says 'Use this when the user wants to remove...' and includes important context about destructive effects, authorization, required permissions, and prerequisites. The parameter description also advises using list-space-repository-links first when needed.

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