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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds only the endpoint path; it does not say what is actually destroyed (e.g., revoking a user's access to the shared webhook data), whether it is reversible, or whether permissions are required for a destructive operation.

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 short fragments with the action front-loaded and no filler. However, the brevity is closer to under-specification than economy, so it does not earn a high conciseness score.

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 no output schema and 0% parameter coverage, the description is too thin. It omits what the delete affects, permission requirements, and the meaning of both required parameters.

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% for the top-level parameters, so the description must carry the burden and does not. It never clarifies whether 'id' is the webhook-data ID or a share ID, nor does it explain the required body.userId beyond the schema's own one-line note.

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 ('Remove') and resource ('webhook share') and pins it down with the HTTP route DELETE /api/v2/webhook/data/share/{id}. This distinguishes it from delete_webhook_bot_share_id and post_webhook_data_share_id by resource, though it never names the siblings explicitly.

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?

No when-to-use, when-not-to-use, or alternative guidance is given. An agent must infer from the route that this is the inverse of post_webhook_data_share_id, and nothing states prerequisites such as owning the share or the data webhook.

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