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

Goes beyond the annotations (destructiveHint, idempotentHint) by disclosing the confirmation protocol — the first call is a non-destructive preview returning confirm_token, and the real deletion only happens on the repeat call. It also clarifies scope of destruction ('The bottle stays on your shelf'), which is exactly the kind of context annotations cannot convey.

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?

Three tight sentences: purpose and id source first, scope guarantee second, the procedural two-step flow last. Every sentence carries non-redundant information and nothing is padded.

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?

With no output schema, the description still covers the key return behavior (the first call returns confirm_token), and it explains the full call lifecycle for a destructive tool. An agent has everything needed to invoke it correctly on both calls.

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%, and the schema already documents both activity_id and the confirm_token two-step semantics, so the description mostly restates it. The description adds no format or edge-case detail beyond the schema, matching the baseline 3 for a fully documented 2-param schema.

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 ('Delete one of your own feed posts') and scopes it to the caller's own content, so it is immediately distinguishable from siblings like delete_collection or remove_bottle. It also names the source of the id (list_my_activity), anchoring the resource precisely.

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?

Gives clear context for use: only for your own posts, id obtained from list_my_activity, and an explicit two-step procedure (first call previews, second call after user agreement). It does not name an alternative tool or state when-not to use it, but the procedural guidance is strong.

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