apps_run

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

Discloses that it patches values and queues on ComfyUI, and that unknown keys fail loudly. However, with no annotations provided, it lacks details on auth requirements, rate limits, or idempotency, which are relevant for a mutation 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?

Three sentences, front-loaded with the main action, no wasted words. Efficient and to the point.

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?

Covers the input format, return value (prompt_id), and polling mechanism. Adequately explains the workflow for an execution tool, especially with no output schema.

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 100%, baseline 3. Description adds meaning by explaining the value format as '<nodeId>.<widget>' and that unknown keys fail loudly. Provides useful context beyond the schema.

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 clearly states 'Run a micro-app once' and explains the process of patching values and queuing on ComfyUI. It distinguishes itself from sibling tools like apps_run_status by mentioning polling for completion.

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?

Provides explicit guidance on when to use: 'Only pass values for inputs listed in the app's appMode.inputs' and mentions polling apps_run_status. Does not explicitly list alternatives, but the context of sibling tools makes usage clear.

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