marketplace_webhooks_delete_instance

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: no statement that this is destructive/irreversible, whether related resources (e.g. webhook deliveries) are affected, or what auth is required. The deprecation marker is the lone behavioral signal.

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?

Front-loading '[DEPRECATED]' is good, but the path text is duplicated verbatim inside the parentheses, which is pure waste, and the brevity comes from missing content rather than disciplined editing.

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?

A destructive operation with no annotations, no output schema, and a bare path string leaves the agent without the prerequisites, side effects, or replacement guidance it needs. The deprecation note is not enough to make this complete.

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?

One parameter with 100% schema coverage, so the schema already documents 'id' fully. Baseline is 3 when the schema does the heavy lifting; the description adds no format, constraint, or meaning beyond what is in the schema.

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 REST path 'DELETE /v1/marketplaceWebhooks/{id}' does identify the verb and resource, so an agent can infer this deletes a marketplace webhook by id. But it never says so in plain language, relying entirely on REST convention, and it is not differentiated from the many other *_delete_instance siblings beyond the resource token in the path.

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 only guidance is the '[DEPRECATED]' tag, which weakly signals 'prefer something else' but names no replacement and gives no when-to-use or when-not-to-use condition. Nothing tells the agent which alternative tool to use instead.

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