cyd_shortcut_delete

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

With no annotations, the description carries full behavioral disclosure burden. It states the deletion but does not disclose irreversibility, error behavior (e.g., missing ID), or any side effects on the home screen or storage. The qualifier 'microSD-backed' adds specificity but not behavioral scope.

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 brief (one sentence) and not bloated, but it lacks substance. While conciseness is good, the structure provides no additional layers of information beyond the bare purpose. It is under-specified rather than efficiently complete.

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?

Given no annotations and no output schema, the description ought to carry the full context. It does not address failure modes, validation rules, or the meaning of 'microSD-backed' in the context of Home shortcuts. For a simple tool this might be minimal, but the lack of behavioral detail leaves gaps for correct invocation.

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 0% description coverage, and the description does not explain the parameter at all. It simply uses 'shortcut_id' without stating what it represents, its format, or that it must reference an existing shortcut. The pattern in the schema is the only clue.

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 names a specific action ('Delete') and a precise resource ('microSD-backed Home shortcut'). It clearly distinguishes from siblings like cyd_shortcut_create and cyd_shortcut_update, which operate on the same object type but with different operations.

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 tool versus alternatives. There is no mention of conditions, prerequisites (e.g., shortcut must exist), or when to prefer update over delete. The context is left entirely to the agent to infer.

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