list_dashboards

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

With no annotations, the description carries the burden and provides some behavioral context through 'bounded pagination' and 'optional title search'. However, it does not explicitly state read-only behavior, return format, or the actual pagination limit, leaving notable transparency 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?

One front-loaded sentence states the action, resource, and key modifiers without any filler. It is concise and well-structured.

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 simple list tool with optional search and pagination, the description covers the essential selection criteria. It could mention return shape or default behavior, but the low complexity and sibling context make the current level adequate.

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?

Since schema description coverage is 0%, the description compensates by clarifying that 'search' targets titles and that page/page_size implement bounded pagination. This adds meaning beyond the bare schema, though it does not elaborate on exact bounds or defaults.

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 uses a specific verb 'List' with resource 'dashboards' and adds relevant modifiers ('optional title search', 'bounded pagination'), making the tool's purpose immediately clear. It distinguishes itself from sibling tools like get_dashboard, create_dashboard, and update_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 implies the tool is for browsing or searching dashboards, but it does not explicitly state when to prefer this over get_dashboard or other list tools. It lacks exclusions or alternative recommendations, so usage guidance remains implicit.

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