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

With no annotations, the description carries the full burden of behavior disclosure. The verb 'Delete' signals a destructive operation, but nothing is said about irreversibility, permissions, side effects on related objects, or behavior when the post doesn't exist.

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 sentence with no redundant content. The action word and target are front-loaded, and there is no ambiguity about the purpose once the schema is consulted.

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?

The tool is simple with one required parameter, so the definition is minimally viable. However, as a destructive operation with no annotations and no output schema, it should probably state whether deletion is permanent, what the response is, and whether related data is affected.

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%, so the description must compensate. 'By ID' clarifies that post_id is the identifier of the post to delete, but the parameter name 'post_id' and integer type already convey most of that meaning, adding little new semantic value.

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?

Description uses a specific verb plus resource: 'Delete a single post by ID.' It distinguishes itself from sibling tools like bulk_delete_listen_items and delete_listen_item through the singular 'post' target and 'single' scope, so an agent can select it correctly without opening schemas.

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 context is only implied by the phrase 'Delete a single post by ID.' No explicit when-to-use, when-not-to-use, or alternative routing is provided, and the description does not mention that bulk deletions would use a different tool.

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