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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's real contribution is the semantic detail that removal is soft: 'The posts themselves stay in the database; only the save is undone.' That materially changes how an agent reasons about reversibility and downstream data availability.

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-loaded and efficient, with the key soft-delete clarification placed early. The only waste is the duplicated cost statement ('Free. Cost: free.'), which repeats the same fact twice.

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 two-parameter mutation with no output schema, the description covers what is needed: what is removed, that data is retained, and what the response reports (removed count and new postCount). Only idempotency and error behavior for invalid post ids are unaddressed.

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 coverage is 100%, so both projectId and postIds are already documented, and the description adds only the phrase 'by postId' without explaining limits, batch size, or behavior for unknown ids. Baseline 3 applies when the schema does the heavy lifting.

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 and resource ('Removes posts from one of your projects') and scopes the target to web-app or API-created projects. It is clearly distinct from add_project_posts and remove_watchlist_profiles, though it never explicitly contrasts itself with those siblings.

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?

Usage is only implied by the verb and the resource scope; there is no explicit guidance on when to choose this over add_project_posts or delete_project, and no prerequisite or warning about bulk removal. An agent can infer the use case but gets no routing help.

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