list_dashboards

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

No annotations are provided, so the description carries the burden. It discloses that visibility is enforced by the user's account, which is useful behavioral context. However, it doesn't mention pagination behavior beyond the count parameter, sorting, or what happens when no dashboards match. The description adds some value but leaves gaps.

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?

Three sentences with no waste. The core purpose is front-loaded, filters are listed compactly, and the wildcard note is a useful addition. Every sentence 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 read-only list tool with no output schema, the description covers the essential behavior: what it lists, visibility constraints, and filtering options. It doesn't describe the return format, but for a list tool this is less critical. The main gap is lack of explicit pagination or sorting behavior, but the count parameter covers the main need.

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 description coverage is 100%, so the schema already documents all four parameters. The description adds context about wildcards and case-insensitive substring matching, which is helpful, but it doesn't significantly go beyond the schema. Baseline 3 is appropriate.

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 lists dashboards visible to the user, with explicit filtering by app, owner, or name/label substring. It distinguishes itself from sibling tools like get_dashboard (which retrieves a single dashboard) and create/update_dashboard (which mutate dashboards).

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 explains when to use this tool: to list dashboards the user can see, with filters. It doesn't explicitly name alternatives or state when not to use it, but the context of sibling tools and the clear filtering guidance make the usage context strong. It could be improved by explicitly contrasting with get_dashboard or check_dashboard_access.

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