thetacog-open

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

The description discloses the auto-refresh behavior on tab focus, which adds value beyond what annotations (none provided) convey. It informs the agent about the tool's observable behavior in the browser.

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?

Two sentences, both front-loaded with essential information: the action and the resource. No extraneous words, efficient and clear.

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 simple tool with one optional parameter and no output schema, the description covers the core functionality and behavior. It could be improved by briefly explaining what 'open' entails (e.g., opens a new browser tab) but is otherwise complete.

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 single parameter is thoroughly described in the input schema (enum values and default behavior). The tool description repeats the same default information without adding new meaning, so it meets the baseline for 100% schema coverage.

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 verb 'Open' and the resource 'HTML dashboard for a room', with a default behavior when no room is specified. It distinguishes from sibling tools like thetacog-switch or thetacog-status by focusing on opening a dashboard in a browser.

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?

While the description mentions defaulting to the current room, it provides no explicit guidance on when to use this tool versus sibling tools. No alternatives or when-not scenarios are given, relying solely on implication.

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