mp_dashboard

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

Reinforces the readOnlyHint annotation by stating 'Read-only; no spawn, no mutate.' Provides additional context on what data is shown and how to interpret it, though no mention of performance or staleness.

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?

Very concise: three sentences covering purpose, safety, and usage examples. Every sentence adds value 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?

Given single parameter with default, existence of output schema, and simple read-only nature, the description provides sufficient context and actionable examples for an agent.

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 description references the window_days parameter in context ('in the last `window_days` and 30d'), adding meaning beyond the schema, but does not fully explain its range or effect. With 0% schema description coverage, this compensates somewhat.

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?

Description clearly states it is a 'one-call rollup' of the entire system, listing specific components like store sizes, loop firing counts, and production metrics. It distinguishes itself from siblings by being a high-level dashboard.

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?

Explicitly notes read-only and non-mutating behavior, and provides concrete examples of when to use (system health check, spotting unproductive loops, detecting backlogs). Could improve by naming alternative tools for specific tasks.

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