sys_dashboard

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

With no annotations provided, the description carries the full burden, and 'read-only' directly discloses that this tool has no side effects. For a zero-parameter read-only summary tool, this is meaningful behavioral context, though it does not describe output content or freshness.

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 just two words plus a parenthetical: no filler, no redundant wording, and the read-only nature is front-loaded. Every word earns its place.

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 no-input, read-only dashboard tool, the description is nearly sufficient. It lacks any detail about what the summary contains or how it differs from sibling status tools, but the simplicity of the operation keeps the gap small.

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 tool has zero parameters, so there is essentially nothing to explain. The baseline for parameter semantics is 4, and the description correctly implies no inputs are needed.

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 identifies the resource as a dashboard summary and explicitly states it is read-only. It lacks an explicit verb like 'get' or 'show,' and it does not differentiate itself from similar read-only stats tools, so it is clear but not fully distinguishing.

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?

There is no guidance on when to use this tool versus alternatives such as show_statistic, sys_health, or sys_info. The description gives no context about when a dashboard summary is preferable, nor any exclusions.

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