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

With no annotations provided, the description carries full burden. It reveals the post is 'hidden' (implying soft deletion), but does not disclose other behavioral traits such as reversibility, permission requirements, side effects on related resources (e.g., comments, votes), or idempotency.

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 a single sentence but includes the redundant phrase 'through the developer API'. It could be more concise (e.g., 'Delete a post by hiding it'). Front-loads the core action but lacks structure.

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?

Given no annotations and minimal description, the tool definition is incomplete for a 2-parameter delete operation. It does not explain return values (despite having an output schema), error cases, or confirm success/failure behavior.

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 0%, and the description adds no information about the parameters ('slug' and 'post_id'). The agent learns only their types from the schema, with no semantic context about their format, constraints, or relationships.

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 tool deletes a post by hiding it, which distinguishes it from creation or editing tools. However, it does not contrast with potential alternative deletion methods (e.g., permanent vs. soft delete), leaving some ambiguity.

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?

No guidance on when to use this tool versus siblings like 'release_post' or 'update_post'. The description does not mention prerequisites, limitations, or contexts where deletion is appropriate.

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