dashboard_agent_runtime

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

No annotations are given, and the description provides no behavioral disclosure. It does not state whether the operation is read-only, how data is scoped or aggregated, or what side effects (if any) exist. The one-line noun phrase adds no actionable behavioral context.

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 extremely brief, but brevity here stems from under-specification rather than efficient conciseness. It is a fragment that omits essential operational meaning and provides no structured information.

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?

With no output schema and no annotations, the description carries full responsibility for explaining tool behavior. It fails to define what 'runtime totals' includes, how the data is computed, what the response format is, or how workspace scoping works. The description is insufficient for an agent to use the tool confidently.

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 schema fully documents the only parameter workspace_id with 100% coverage, so the baseline is 3. The description adds no further meaning to the parameter, but the schema already explains the semantics adequately.

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 'Agent run-time totals' is a noun phrase that essentially restates the tool name. It lacks a verb specifying the operation (e.g., get, list, fetch) and does not indicate whether this is a read, query, or summary action. It also fails to distinguish this tool from sibling dashboard and runtime tools.

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?

No guidance is provided on when to use this tool versus alternatives such as dashboard_usage_daily, dashboard_usage_by_agent, or get_runtime_usage. The description offers no context for selection or exclusion.

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