org_dashboard

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

Annotations already declare readOnlyHint=true. The description adds behavioral context about visibility limitations (limited to 3 agents in free preview) and what data is shown, going beyond the annotation.

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?

Two concise sentences: first states the dashboard's content, second explains access modes. No filler, front-loaded with key info.

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 dashboard's complexity and lack of output schema, the description covers main aspects (metrics shown, access limits). Minor gap: does not explain how 'limited to 3 agents' manifests in output.

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% for the single parameter windowHours with a clear description. The tool description does not add any additional meaning beyond the schema's parameter description.

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 states it is an org-wide multi-agent dashboard showing specific metrics, distinguishing it from a potential personal dashboard (sibling 'dashboard' exists). The verb 'shows' and resource 'dashboard' are clear.

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 implies usage for org-wide visibility but does not explicitly compare to alternatives like 'dashboard' or other reporting tools. The mention of 'Team rollout' vs 'Free preview' provides context but no direct when-to-use guidance.

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