Create stage dashboard

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

Annotations indicate readOnlyHint=false, destructiveHint=false, openWorldHint=true. The description adds substantial behavioral context: it creates a Web Server DAT and callbacks DAT, the page POSTs control changes back to the server, and it details security risks. No contradiction with annotations.

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 a single dense paragraph that efficiently covers purpose, components, security, and prerequisites. Every sentence contributes essential information without redundancy.

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 tool with 6 parameters and no output schema, the description provides sufficient context to use it correctly. It explains the resulting dashboard's behavior, security requirements, and dependencies on other tools (manage_cue, create_control_panel, create_panic). No gaps are apparent.

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%, but the description adds meaningful context beyond the schema. For example, it explains that the target COMP holds cues and safety toggles, that the port should avoid conflicts, and that cues become buttons that 'instantly recall' cues. This adds value, though the schema already provides good descriptions.

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 the tool's purpose: 'Serve one unified live-performance cockpit from a Web Server DAT' and enumerates the components (cue-launch buttons, master faders, PANIC button, live readout). It distinguishes from sibling tools like 'create_phone_remote' and 'create_control_panel' by referencing them in context.

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 explicitly states when to use (for a live-performance cockpit), security caveats ('listens on all interfaces and accepts writes with NO auth... use it only on a trusted network'), and prerequisites ('Store cues with manage_cue, expose params with create_control_panel, and run create_panic first').

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