search_all_dashboards

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

The description discloses a meaningful behavioral trait: it retrieves at most 200 dashboards from the API and then filters locally. Since no annotations are provided, this is important information for the agent, as it warns about potential incomplete results for large result sets. Pagination and error behavior are not described, but the key limitation is clearly stated.

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 compact and front-loaded: it states the purpose, the key implementation detail, and the intended use case in two short sentences. There is no redundant or filler content.

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 tool with only two optional parameters and completely documented schema, the description provides the essential context: what it does, how it behaves at scale, and when to prefer it. The absence of an output schema means return shape is not described, but for a search tool this is a relatively minor gap.

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%, with both parameters already having clear descriptions in the input schema. The tool description adds no additional parameter-specific details, so the baseline score of 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 states a concrete action ('Search through dashboards') with a specific resource and adds a distinguishing detail: local filtering with a 200-dashboard cap. It is clear and understandable, though it does not explicitly name sibling tools like get_dashboards to contrast the difference.

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?

'Better for complex searches' provides clear guidance on when to prefer this tool, implying it is the right choice when server-side filtering or simple listing is insufficient. However, it does not explicitly mention alternatives or state when NOT to use it.

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