List Dashboards

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

Annotations already confirm it's read-only, idempotent, non-destructive. The description adds that it includes share state, providing behavioral context. It does not mention pagination or ordering, but given zero parameters, this is acceptable.

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?

Single sentence, no wasted words, directly conveys core purpose and a distinguishing feature (share state). Front-loaded and 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?

The tool is simple with no parameters, and the description covers its purpose and a key output detail. An output schema exists to document return values, so the description is sufficiently complete for selection and invocation.

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?

No parameters exist, and schema coverage is 100% (no params to document). The description adds no input semantics but is acceptable for a parameterless tool.

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 action (list), the resource (all analytics dashboards), and the scope (caller can access), with additional detail on share state. It distinguishes from siblings like get_dashboard (single dashboard) and create_dashboard.

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 implicitly indicates when to use (when needing all accessible dashboards with share state) but does not explicitly state when to choose alternatives like get_dashboard for specific details or list_dashboard_widgets for widget details. No when-not-to-use guidance.

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