Delete Link

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

The description lists permissions, deprecation, and irreversibility. However, the contradictory statements about recycle bin vs permanent delete undermine trust. Annotations already indicate destructiveHint=true, so the description adds context but is inconsistent.

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 longer than necessary with repetitive phrases ('This cannot be undone' appears twice). The inclusion of the full endpoint URL is detailed but not essential. Could be more concise.

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?

Given the simple delete operation with good annotations, the description should clearly communicate the deprecation and proper usage. The internal confusion and lack of clear V2 recommendation make it incomplete for an agent to reliably use.

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 input schema (100% coverage). The description merely restates that they are required without adding new semantic meaning, so baseline score of 3 is appropriate.

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 starts by saying 'Send a specific Project Home Link to the recycle bin' but later states 'Use this to permanently delete... This cannot be undone.' This contradiction obscures whether the tool moves to recycle bin or permanently deletes, reducing clarity.

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?

While it notes required permissions and deprecation, it does not provide guidance on when to use this tool versus alternatives like the V2 endpoint or other delete tools. The deprecation warning suggests avoiding it, but no explicit 'use V2 instead' directive is given.

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