subscriber_delete

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

The description only states that the tool deletes, indicating a destructive action, but no annotations are provided. It omits behavioral details such as whether the deletion is permanent, any side effects, or required permissions.

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 very concise at one sentence and front-loaded with the key information. It wastes no words, but could be slightly more informative without losing conciseness.

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 tool is simple with one parameter and has an output schema, the description fails to mention what the tool returns or what happens if the subscriber does not exist. It lacks important context for proper invocation.

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?

The description adds minimal meaning to the single parameter 'id' by specifying it is used to identify the subscriber. Since schema description coverage is 0%, this extra context is helpful but still basic.

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 clearly states the action (delete) and the resource (subscriber) with the identifier method (by ID). It effectively distinguishes itself from sibling tools like subscriber_create, subscriber_get, subscriber_list, and subscriber_update by specifying the delete operation.

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 guidance is provided on when to use this tool vs alternatives or any prerequisites. For example, it doesn't mention that the subscriber must exist or that this operation is irreversible.

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