delete_transformation_project

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

Displays destructive warning and valid identifier requirement. No annotations provided; lacks details on side effects, permissions, or failure behavior. Basic but not rich.

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?

Single sentence with warning front-loaded. No extraneous words, every part adds value.

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?

Adequate for a simple delete tool with two parameters and no output schema. Could mention what happens if identifier is invalid or if there are dependencies, but not critical.

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?

Both parameters documented in schema (100% coverage). schema_file description adds required confirmation step beyond type definition, providing extra guidance for proper usage.

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?

Clearly states 'Deletes transformation project' with a specific verb and resource. Distinct from sibling tools like create or modify.

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?

Explicitly warns 'DESTRUCTIVE - Confirm with user before calling', giving clear usage context. Could mention alternatives like modify_transformation_project for non-destructive changes.

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