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

With no annotations, the description carries the full burden and does useful work by scoping the destructive effect to the farm account only and clarifying that the platform account is untouched. It also states the authorization precondition ('authenticated user is allowed to manage'). It does not disclose irreversibility or downstream effects on submissions, but the core behavioral boundary is clearly communicated.

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 tight sentences with no filler. The primary action and scope are front-loaded, and the critical caveat about not deleting the platform account is in the second sentence. Every clause earns its place.

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 one-parameter delete tool with no output schema, the description is largely complete: it states the target resource, authorization scope, supported platforms, and the key non-effect. The main gaps are unspecified consequences or return behavior after deletion, but given the low complexity, these are minor rather than blocking.

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 100%, so the schema already documents account_id. The description adds the platform list (TikTok, Instagram, YouTube) and the 'allowed to manage' constraint, which gives slight extra context. However, it does not explain where to find the ID or any ID format expectations, so the added value beyond the schema is modest.

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 names a specific verb and resource ('Delete a posting account') and adds the exact scope: authenticated-user-managed accounts across TikTok, Instagram, or YouTube. This clearly differentiates it from sibling tools like delete-submission-tool and update-account-tool without needing to inspect their 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?

The description gives clear context for when to use the tool: deleting a managed posting account from the farm. It also states an important exclusion ('does not delete the account on the platform itself'), which prevents misuse. It does not explicitly name alternative tools, but the resource-level clarity makes the intended use obvious.

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