delete-object

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

The description adds significant behavioral context beyond the destructiveHint annotation. It explains the irreversible nature of deletion, the specific permission model (creator or admin), and the group deletion behavior for threads. This fully satisfies transparency needs.

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 concise and well-structured: it starts with the primary action, then lists target types with their effects, includes a caution about reversibility, and ends with permission notes. Every sentence is necessary and information-dense.

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 the tool's complexity (multiple object types, destructive effect, permission constraints) and the presence of an output schema, the description fully covers all necessary information. It addresses usage, parameters, side effects, permissions, and failure conditions.

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%, but the description adds important semantic details: for targetType it explains the implications of each value (thread deletes all comments), and for targetId it clarifies it refers to the ID of the object being deleted. This enhances the schema definition.

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 tool's purpose: permanently deleting a Twist object. It specifies three distinct target types (thread, comment, message) and explicitly distinguishes itself from sibling tools like update-object by emphasizing permanent deletion.

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 provides detailed usage guidance: how to use each targetType, the necessity of passing targetId, a warning about irreversibility with a user confirmation requirement, and permission prerequisites (creator or admin). This fully informs when and how to use the tool.

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