list_dashboards

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

No annotations are provided, so the description bears full responsibility. It indicates the return format (Markdown list) but does not disclose potential side effects, pagination, sorting, or rate limits. It adequately implies a read-only operation but could be more explicit.

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, with a clear purpose statement and structured Args/Returns sections. Every sentence adds value; no redundant or unnecessary text.

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 and sibling tools, the description provides sufficient information for most use cases. It covers output format and key parameters, though it omits details on sorting or pagination. Overall, it is fairly complete.

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?

Although schema coverage is 0%, the description adds meaningful context for both parameters: 'collection_id: Optional collection ID to filter by' and 'limit: Maximum number of dashboards to return (default 100).' This goes beyond the schema's bare type definitions.

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 'List all dashboards accessible to the current user,' specifying the verb (list), resource (dashboards), and scope (accessible to user). This distinguishes it from sibling tools like get_dashboard (single) and search_dashboards (search).

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 mentions optional filters (collection_id, limit) but does not explicitly state when to use this tool versus alternatives or when not to use it. It provides clear usage context but lacks explicit guidance on exclusion.

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