studio_delete

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

The description explicitly states the action is irreversible and requires user confirmation (confirm=True). Without annotations, it adequately conveys the destructive nature of the tool.

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 extremely concise with three lines, front-loading the essential information: action, irreversibility, and parameter requirements.

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?

The description does not explain return values, but output schema exists. It does not distinguish between deleting a studio artifact versus the entire notebook, which could be ambiguous given sibling notebook_delete.

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 adds significant meaning beyond the input schema by explaining that notebook_id is a Notebook UUID, artifact_id is an Artifact UUID from studio_status, and confirm must be set to True after user approval.

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 deletes a studio artifact, using specific verb and resource. It distinguishes from sibling tools like studio_create and studio_revise by being the delete operation.

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 prerequisite context (artifact_id from studio_status) and the confirm parameter requirement, but does not explicitly tell when to use this tool versus alternatives like notebook_delete or source_delete.

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