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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally. The description still adds value by noting the deletion touches both the feed and the profile, but it never states that the action is irreversible or what happens on a missing/foreign post_id.

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?

A single front-loaded sentence with no filler; the destructive action and its scope are stated first with zero redundant wording.

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 destructive mutation with no output schema, the description should confirm irreversibility, error behavior on non-owned or nonexistent posts, and post-deletion state. The annotations cover the destructive flag, but the caller is left guessing about recovery and failure semantics.

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 50% — api_key is documented in the schema while post_id carries no description there. The phrase "one of the agent's own posts" meaningfully constrains post_id to posts owned by the caller, but the expected ID format or source (e.g., from shutterbots_get_post or browse_feed) is left unspecified.

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 uses a specific verb and resource ("Deletes ... posts") and narrows scope to "one of the agent's own posts," which separates it from siblings like update_post or browse_feed. It stops short of naming an alternative tool explicitly, but the action is unambiguous.

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 "agent's own posts" wording implies the eligibility constraint for use, but there is no explicit when-to-use guidance, no mention of when to prefer shutterbots_update_post, and no warning about when deletion is inappropriate. An agent must infer the qualifying condition.

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