cyd_app_delete

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

With no annotations, the description carries the behavioral burden. It transparently states the operation is permanent and includes the cascading shortcut cleanup. However, it does not mention prerequisites, error behavior, or consequences for a currently running app.

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 core sentence is compact and front-loaded with the action and scope. The opening fragments 'Machine-specific (cyd). Action, L1.' add little value and could confuse an agent, but overall the definition is efficiently sized.

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 single-parameter destructive tool, it gives the essential effect and cascade behavior. Still, without annotations or an output schema it omits what happens on failure, whether deletion is recoverable, and any access or runtime prerequisites.

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 0% and the description never addresses the app_id parameter semantically. It says 'one installed MicroPython app' but does not clarify that app_id is the identifier, its format, or how it relates to app names shown in listing tools.

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 ('delete') with a clear resource ('one installed MicroPython app') and a precise behavioral scope ('and any Home shortcut that targets it'). This distinguishes it from siblings like cyd_shortcut_delete and cyd_apps_list.

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 is given for when to use this tool versus alternatives such as cyd_shortcut_delete or cyd_app_deploy. The phrase 'Machine-specific (cyd). Action, L1.' does not convey usage context or exclusions.

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