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

The description says 'Delete one post from a project', which implies a destructive mutation, while the annotations declare destructiveHint=false. That is a direct contradiction on a core safety signal. The additional notes about membership and one KV write do not resolve the inconsistency.

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 short, front-loaded with the core action, and mostly free of waste. The phrases 'One KV write' and 'The page review is unchanged' add some behavioral context but are cryptic and could use more clarity.

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?

It covers the core operation, a permission precondition, and a brief side-effect note, which is helpful. However, it does not explain return behavior or error conditions, and the destructiveHint contradiction leaves an important safety aspect unresolved.

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 parameters are already documented in the schema. The description does not add syntax, format, or validation details beyond what the schema provides.

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 states a specific verb and resource: deleting one post from a project. It clearly distinguishes the operation from sibling tools such as add_post and update_project.

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?

It gives a permission precondition ('The caller must be a member'), which is useful context. However, it does not explicitly state when to use this versus alternatives or when not to use it, leaving usage mostly implied by the tool name.

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