hamravesh_delete_app

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

Discloses irreversibility, permission requirement, disabled default, and dry_run option. Without annotations, description carries full burden and does so reasonably well. Missing details on return values or error handling.

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?

Short and packed with key info (action, irreversibility, permission, dry_run). Front-loaded with 'complete deletion'. Some technical details could be reorganized, but overall efficient.

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 delete tool given sibling context. Lacks parameter explanations and output/return info. Schema and output schema are minimal, so description should compensate more.

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?

No parameter descriptions in schema (0% coverage). Description does not explain app_id or org. Fails to add meaning beyond schema, which is critical for low coverage.

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?

Description clearly states 'complete deletion' and 'irreversible', identifying the action and resource. It distinguishes from sibling tools (no other delete app tool). However, 'Darkub app' is not fully explanatory for external users.

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?

Mentions requirement for ALLOW_DELETE permission and that the tool is disabled by default (requires HAMRAVESH_ALLOW_WRITE=1). Mentions dry_run preview mode. Does not explicitly compare with alternatives, but siblings are mostly non-deletion actions.

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