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

With no annotations, the description carries the full burden and does disclose that this is a destructive operation (revoke + delete) against persistent storage (Cloudflare D1) and that it is gated by ownerToken. However it stops short of stating irreversibility, whether the share record is removed from the sharing index, or what happens with an invalid/expired token.

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?

A single front-loaded sentence with the action first, the target second, and the credential last. No filler, no restatement of the tool name.

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, unannotated, output-schema-less tool this is on the thin side: an agent learns what it does and what credential it needs, but not the reversibility profile, failure modes, or confirmation semantics that matter for an irreversible delete.

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 both required parameters and the optional apiUrl are already documented in the schema. The description adds only the fact that ownerToken is the authorizing credential for the delete, which is marginal value beyond the schema's own 'Owner token received when creating the share'.

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 pair (revokes and deletes) against a specific resource (a shared drawing), plus the mechanism and required credential. This clearly separates it from sibling share-management tools such as cad_share_drawing, cad_update_shared, and cad_open_shared.

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 gives no when-to-use framing, no mention of when not to use it, and no pointer to alternatives like cad_update_shared for non-destructive changes. The only contextual cue is the ownerToken requirement embedded in a sentence about purpose, which is incidental rather than guidance.

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