delete_story

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

The term 'soft-delete' hints at behavior (not permanent deletion), but no additional details are provided. There is no disclosure of side effects, reversibility, or required permissions. Since no annotations are present, the description carries full responsibility and falls short.

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, concise sentence. It is front-loaded with the action. However, it is too brief, lacking necessary context. While it earns its place, it sacrifices completeness for brevity.

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 tool with one parameter and no output schema, the description should explain what 'soft-delete' means, success/error indicators, and any side effects. It fails to provide a complete picture, making it insufficient for an agent to fully understand the tool's behavior.

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?

The description only repeats the parameter name 'slug' without adding any meaning. Schema coverage is 0%, and no format, constraints, or examples are provided. The description adds no value 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 clearly states the action ('soft-delete') and resource ('story'), and specifies the identifier ('by slug'). It distinguishes from sibling tools like delete_session and delete_solution by resource type. However, it does not elaborate on what 'soft-delete' entails.

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 guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., slug must exist) or scenarios where this tool is appropriate or inappropriate.

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