Delete an activity post

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

The description discloses the login requirement, irreversible deletion, and error behavior on re-deletion. These details go beyond the annotations (which only indicate destructive and non-idempotent) by adding concrete operational constraints.

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 sentences, front-loaded with the login requirement, and each sentence provides essential caveats without redundancy. This is concise and well-structured.

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 simple one-parameter delete tool, the description covers purpose, auth, irreversibility, and error behavior. With an output schema present and complete parameter documentation, no significant gaps remain.

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 schema covers the single 'id' parameter at 100% with provenance details (e.g., from get_user_activity or post_text_activity). The description itself adds no parameter-level meaning, so the baseline of 3 is appropriate.

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 ('Delete') and resource ('activity post') with an ownership qualifier, distinguishing it from siblings like delete_thread and delete_thread_comment. The title and description align 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?

The description sets clear context: it requires login and targets the authenticated user's own activity post. It implies the appropriate use case without explicitly naming alternatives or exclusions, which is strong but not exhaustive.

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