cyd_run

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

With no annotations, the description carries the burden of behavioral disclosure. It does disclose the central behavior—pausing the app and advancing a bounded number of update frames—which is real context beyond the tool name. However, it does not clarify whether the app remains paused afterward, what side effects frame advancement may have, or what the operation returns.

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 short and mostly front-loaded, with the core mechanism in the second sentence. However, 'Control, any layer.' is a cryptic fragment that does not earn its place and the first sentence adds little beyond the tool name.

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 tool, the core invocation information is present: what it does and what the frame count means. But there is no output schema, no post-condition clarity, and no orientation against the large cyd_* sibling family, leaving some contextual gaps.

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 coverage is 0%, so the description must explain the single parameter, and it does: 'frames' clearly corresponds to the number of cyd.update() frames granted. This fully compensates for the missing schema descriptions and adds meaning the schema alone does not provide.

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 gives a concrete action: pause the cooperative MicroPython app and grant a bounded number of cyd.update() frames. This distinguishes it from a generic 'run' command and from siblings like cyd_pause or cyd_step. The phrase 'Control, any layer' is vague, but the main clause is specific enough.

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?

There is no guidance on when to use this tool versus the many closely related siblings such as cyd_pause, cyd_resume, or cyd_step. 'Machine-specific (cyd)' is a scope warning, not usage direction, and no alternative or exclusion is mentioned.

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