Delete one or more stories

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

Annotations already declare destructiveHint=true, indicating this is a destructive operation. The description adds the constraint that only stories 'previously posted' by the user are affected, which is a useful scoping detail. However, it does not disclose permanence, authorization requirements, or side effects. No contradiction with annotations.

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, short sentence (5 words) that is front-loaded with the main action. It is very concise. However, it is so minimal that it borders on under-specification, though it does convey the core purpose effectively.

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 destructive tool with 3 parameters (one required) and no output schema, the description is incomplete. It omits parameter semantics, whether the deletion is permanent, how story IDs are used, and any effect of the peer or accountId parameters. The annotations cover destructiveness, but the description alone is insufficient for safe and correct invocation.

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 does not explain any of the parameters (peer, storyIds, accountId). It offers no additional meaning beyond the parameter names and types in the schema. This is a significant gap, as the description should compensate for the lack of schema-level descriptions.

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 the action clearly: 'Remove stories you previously posted.' It identifies the resource (stories) and the verb (remove). It does not explicitly distinguish from sibling tools like delete_messages, but the resource is distinct. There is slight ambiguity about whether the 'previously posted' restriction is accurate, given the 'peer' parameter.

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 implies usage: when you want to remove stories you have posted. It does not explicitly mention alternatives or when not to use it. The 'previously posted' scope provides some contextual guidance, but there is no explicit comparison to other deletion or management tools.

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