delete_appRetire définitivement une app de la plateforme. Son URL cessera de fonctionner. Demandez confirmation à l'utilisateur avant d'appeler cet outil.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | ||
| secret_token | No | Le jeton secret (maam_app_…) renvoyé lors de la publication de cette app. Facultatif si l'app est rattachée au compte de la clé API configurée. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the transparency burden. It discloses permanent removal, URL invalidation, and the need for user confirmation. It does not detail data cascade or ownership requirements, but the core destructive behavior is transparent.
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 three short sentences, each adding value: permanence, effect on URL, and user confirmation. No fluff or redundant repetition.
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 a destructive delete operation, the description covers permanence, side effect, and confirmation step. It does not mention authentication/ownership details or what happens to associated data, but these are secondary for the core action.
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 description coverage is 50%: the 'secret_token' parameter has a description in the schema, but 'slug' has none. The tool description adds no parameter-specific meaning, relying on schema and parameter names, which are adequate but not enriched.
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 uses a specific verb and resource: 'Retire définitivement une app de la plateforme' clearly indicates permanent deletion. It also clarifies the consequence ('Son URL cessera de fonctionner'), distinguishing it from sibling tools like update_app.
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 clear context that the operation is permanent and destructive, and explicitly instructs to 'Demandez confirmation à l'utilisateur avant d'appeler cet outil.' It does not mention alternative tools, but the deletion intent is unmistakable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a clearly distinct resource and action: app metadata, app data, publishing, claiming, listing, deletion, and the guide. get_app and get_app_data are separated by metadata vs user JSON, and update_app vs set_app_data are separated by HTML/title vs stored data.
All tool names follow the same verb_noun pattern in snake_case: claim_app, delete_app, get_app, get_app_data, get_publishing_guide, list_my_apps, publish_app, set_app_data, update_app. The convention is perfectly consistent.
Nine tools is well-scoped for the domain of publishing and managing single-file HTML apps with data persistence. Each tool serves a distinct lifecycle stage or data operation, with none feeling redundant or extraneous.
The set covers the full lifecycle: publish, read metadata, update, delete, claim, and list; plus data operations (get/set app data) and an explicit guide for the tricky data-evolution pattern. No obvious missing operation blocks the intended workflows.