list_dashboards

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

No annotations exist, so description carries full burden. It describes the listing behavior and response modes but does not discuss permissions, rate limits, or side effects. Since it is a read-only list, this is acceptable but not fully comprehensive.

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 concise and front-loaded with purpose. It uses a clear bullet-like format for arguments. Every sentence adds value, but the structure could be slightly improved with more explicit labeling.

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 presence of an output schema, the description does not need to detail return values. It covers the purpose, usage context, and parameter details. It adequately informs an agent for correct invocation, though mentioning workspace scope is already done.

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 0%, but the description fully explains both parameters: response_mode with its three options (compact, standard, full) and name_contains as a case-insensitive substring filter. This adds significant meaning beyond the schema.

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 'List dashboards in the current workspace' with specific verb and resource. It further distinguishes from siblings by guiding the agent to use this tool first to discover IDs, then use get_dashboard for details.

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 states when to use this tool: 'Start here to discover dashboard IDs, then use get_dashboard for detail on a specific one.' This provides clear context, though it does not mention exclusion cases or alternative list tools.

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