cyd_shortcuts_list

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

No annotations are provided, so the description must carry the behavioral burden. The word 'Observation' hints at a read-only operation, but the description does not explicitly state side effects, permission requirements, or whether it modifies internal state. This is passable but thin for a non-annotated tool.

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 compact: one context sentence, one functional sentence. It front-loads the actual list behavior and avoids filler. The initial 'Machine-specific (cyd). Observation, L1.' is slightly cryptic, but it adds context without wasting space.

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?

With no output schema, the description tells the agent that shortcuts are listed but does not describe the returned value shape, fields, or possibly empty/normal conditions. For a simple zero-parameter read this may still be callable, but the agent is left guessing about the output format.

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 tool has zero parameters and a fully covered empty schema, so there are no parameter semantics to enrich. Per the baseline for no parameters, a score of 4 is appropriate; the description cannot add more because there is nothing to parameterize.

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 ('List') and a distinct resource ('microSD-backed Home shortcuts'), which unambiguously identifies the operation. It also has clear distinct siblings (cyd_shortcut_create/update/delete), so an agent can tell this is the read-only listing variant without opening schemas.

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 labels this as an 'Observation, L1', implying a read-only inspection use, but it never explicitly states when to use it over related tools such as cyd_home, cyd_apps_list, or cyd_shortcut_*. There are no exclusions or alternative tool names, so selection guidance is left to inference.

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