bardo_dashboard

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

Annotations indicate readOnlyHint=true, which is consistent with the read behavior. The description adds value by detailing the returned data (note counts, notices, tags, pinned notes, policy), 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?

The description is a single, information-dense sentence that front-loads the purpose and enumerates contents. It could be broken into a bulleted list for readability, but it remains efficient.

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?

Without an output schema, the description provides a comprehensive list of returned items. It covers the essential aspects of the dashboard, though it omits details like data format or limits.

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 (session_token) has 0% schema description coverage and is not mentioned in the description. The code likely uses it for authentication, but the description provides no guidance on its usage or meaning.

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 the tool returns a dashboard with specific data points (note count vs limits, unread notices, tags, pinned notes, policy) and contrasts with making several separate calls. It effectively distinguishes from siblings like bardo_notes_list and bardo_policy_get.

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 use when a broad orientation is needed, explicitly mentioning it replaces multiple round trips. It does not provide explicit exclusions or when to use individual tools, but the contrast with separate calls gives clear context.

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