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

The description adds substantial behavioral context beyond the annotations: deletion is permanent and cannot be undone, only unpublished Pins are eligible, and published Pins cannot be deleted through Tailwind. It also warns against arbitrarily choosing an account, which is important for a destructive mutation.

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 front-loaded with the primary action and scope, followed by clear alternative-tool routing and account-selection guidance. Despite its length, every sentence carries useful decision or safety information.

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 a destructive mutation with rich annotations, a complete input schema, and an output schema, the description covers the key risks, eligibility constraints, and alternative tools. Nothing material for correct invocation appears to be missing.

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 both parameters are already well documented. The description repeats that postId comes from create_post or list_posts and adds account-selection guidance, but does not add much semantic detail about the parameter values themselves beyond the 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?

The description states a specific verb and resource: permanently deletes an unpublished Pin by postId. It immediately clarifies the critical scope restriction — only unpublished Pins, not published ones — which distinguishes it from generic delete tools and makes the operation unambiguous.

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?

It gives explicit when-to-use guidance and names alternatives: use update_post to change metadata, create_post for image changes, and unschedule_post to keep a scheduled Pin. It also specifies an account-selection workflow when multiple accounts exist, leaving little to inference.

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