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

Annotations declare destructiveHint=true and idempotentHint=true, but the description goes well beyond them: exactly what is destroyed (public page, project links) versus preserved (documents, their links and analytics), the 30-day reversibility window, permanent purge after, and the confirmation preview flow. This is the level of disclosure a destructive, open-world mutation needs.

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 delete action and its scope are front-loaded, then restore window, alternative, tier effect, and confirmation flow follow in a tight sequence with no filler. It is dense but every sentence carries actionable information; only the trailing untrusted-content note reads as boilerplate.

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, no-required-param tool with no output schema, the definition covers effect on related resources, reversibility and its time limit, downstream purge, tier impact, the confirmation mechanism, and the sibling alternative. An agent has everything needed to invoke it correctly and warn a user.

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 100%, so the baseline is 3. The description adds meaning the schema does not: it explains that LinkDrop shows a preview (project, document count, public-page status) before acting, which is what confirm and confirmationToken refer to, tying the parameters to a concrete human-in-the-loop flow.

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 opens with a specific verb+resource ("Delete a project") and immediately delineates scope: documents survive, the project and its links stop resolving. It is easily distinguished from lnkdrp_remove_doc_from_project and lnkdrp_restore_project without opening any 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?

It names two alternatives and the conditions that select them: lnkdrp_restore_project for undo within 30 days, and lnkdrp_remove_doc_from_project when only single documents should leave while the project stays. It also states the Free-tier consequence, giving an agent enough to decide whether deletion is the right call.

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