deletePostCallAction

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is known. The description usefully adds blast-radius context ('The agent's other actions are not changed'), but says nothing about irreversibility, required permissions, or what happens if the action_id is invalid.

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 short sentences, front-loaded with the operation and followed by the scoping caveat; nothing is buried. The trailing '(Tags: Agents)' fragment is metadata padding that earns no place in the prose.

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 two-parameter destructive tool with full schema coverage and annotations covering the safety profile, the description is nearly sufficient. It is missing only where action_id comes from and an irreversibility confirmation, which are minor against the structured data already present.

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 100%, so both required parameters (agent_id, action_id) are fully documented in the schema. The description adds no format, range, or sourcing information beyond that, which is the expected baseline when the schema does the work.

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?

States a specific verb ('Remove') and resource ('one post-call action from the agent'), and the second sentence scopes the effect to a single item. It does not name the sibling tools it sits beside (addPostCallAction, updatePostCallAction, listPostCallActions), but an agent can still tell what this does and how its blast radius is bounded.

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 when-to-use or when-not-to-use guidance. Nothing tells the agent to use listPostCallActions to obtain the action_id first, nor how this differs from updatePostCallAction, which is the natural sibling confusion point.

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