tealfabric_delete_webapp

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

No annotations are provided, so the description carries the full burden, yet it discloses nothing beyond the verb. It doesn't say whether the deletion is permanent, whether published versions are removed with it, whether a confirmation or special permission is required, or what happens to a webapp that is currently published.

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?

One short, front-loaded sentence with no filler. It is efficient but borders on under-specified rather than truly concise.

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 an irreversible mutation with zero annotation coverage and no output schema, the definition is too thin. An agent cannot tell what success looks like, whether the action cascades, or how it differs from unpublishing.

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 schema has full coverage of the single webapp_id parameter, and its description states it is a UUID. The tool description adds only 'by ID', which confirms the resource is identified by that field but adds no format or sourcing detail 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?

States a specific verb and resource (delete a Tealfabric webapp) plus the identifier used. It distinguishes 'delete' from siblings like tealfabric_update_webapp, though it does not distinguish it from tealfabric_unpublish_webapp, which is the nearest ambiguity.

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 versus tealfabric_unpublish_webapp or tealfabric_delete_process, and no prerequisites such as ownership or permissions. The only cue is the verb itself, leaving the agent to infer the destructive path.

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