start_dashboard

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates the tool provides instructions (likely read-only), but does not clarify side effects, safety, or whether it actually launches a process. Critical context like authentication needs or state changes is missing.

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 (4 lines) but the initial sentence is vague ('Get instructions'). Key details like the dashboard purpose and prerequisite are present, but the structure could be improved by placing the most actionable information first.

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 one optional parameter and an output schema (unseen), the description is minimally sufficient. It covers the tool's purpose and a prerequisite, but lacks details on the output format, expected behavior, or any usage notes. Completeness is adequate for a simple tool but leaves room for improvement.

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 only parameter 'port' is described in the Args section as 'HTTP port for the dashboard (default: 8080)', which merely restates the schema's default and type. With 0% schema description coverage, the description adds no meaningful semantic context beyond what the schema already conveys.

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 states 'Get instructions to start the web dashboard,' clearly indicating the tool provides guidance for launching the dashboard. It distinguishes from sibling tools like 'start_metrics_endpoint' by focusing on the web UI, though it could be more explicit about the verb (provide vs start).

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 mentions the prerequisite 'pip install mcp-telecom[dashboard]' but does not specify when to use this tool versus alternatives. Since no sibling tool serves the same purpose, the usage context is implied but lacks explicit guidance on conditions or disclaimers.

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