Open Insight Dashboard

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

Discloses first-run dependency installation (~30s), default port behavior, and that sessionDir/contentDir override environment variables for diagnostics or pointing to other project data. No annotation contradiction.

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?

Efficiently packed with useful information, though slightly lengthy; front-loads main purpose, then details. Could trim a bit but still concise overall.

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?

Given the complexity (5 params, no annotations, no output schema), the description fully covers usage, behavior, and edge cases, making it complete for an agent to use correctly.

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%, so baseline is 3. Description adds meaning by explaining defaults, override behavior, and diagnostic use cases for directory parameters, raising it to 4.

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?

Clearly states it opens the Insight dashboard for session analytics, and explicitly distinguishes from ctx_search for natural-language queries.

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 alternative (use ctx_search for queries), explains first-run installation vs subsequent instant opens, and details port and directory overrides for multi-install or sibling project use.

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