ghost_delete_newsletter

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

With no annotations, the description carries the full burden. It explicitly states the operation is permanent and cannot be undone, which is a critical behavioral trait. However, it does not mention authorization needs, rate limits, or what happens if the ID is invalid or the newsletter doesn't exist.

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 concise sentences, no fluff. Every word adds value: the action, resource, method, and consequence. Front-loaded with the verb 'Deletes'.

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?

The tool is simple (1 param, no output schema), and the description covers the essential purpose and consequence. However, it lacks information about return values (e.g., success confirmation) and error behavior, which would be helpful for an agent. Given no output schema, completeness is moderate.

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 only parameter 'id' is described merely as 'by ID' in the description. The schema provides a pattern (24-character hex), but the description adds no further meaning, such as format hints or example. With 0% schema description coverage, the description should compensate but fails to do so.

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 ('deletes a newsletter') and the resource ('newsletter from Ghost CMS'), with the specific method ('by ID'). This distinguishes it from sibling tools for other resources (e.g., ghost_delete_member, ghost_delete_post) and from create/update/get operations.

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 does not provide guidance on when to use this tool versus alternatives. For example, it doesn't mention that this is for permanent deletion only, and that a temporary disable could be achieved via ghost_update_newsletter. No context on prerequisites or when not to use it.

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