splunk_list_dashboards

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

No annotations exist, so the description carries the full burden, yet it discloses nothing about permissions required, whether the listing is complete across apps by default, ordering of results, or pagination behavior. The only behavioral hint is that both dashboard formats are included.

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 purpose sentence is front-loaded and the Args block is compact with no filler. The parenthetical about dashboard formats is arguably optional but adds discriminating information.

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?

An output schema exists so return values need not be described, but with zero annotation coverage and zero schema descriptions, the description should still say more about the paging model (count default/max, how offset interacts) and the app filter's accepted values.

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 0%, so the terse Args block does real work: it clarifies that app is an app filter, count is the number of dashboards to retrieve, and offset is the pagination offset — none of which are documented in the schema itself. Still missing are any bounds on count and what values app accepts.

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?

States a specific verb and resource ("List dashboards in the Splunk instance") and adds a distinguishing detail that the listing covers both Simple XML and Dashboard Studio dashboards. It never explicitly contrasts with splunk_get_dashboard or splunk_search, but the operation is unambiguous.

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 intent of listing is implied by the description, and the 'app' arg hints at narrowing scope, but there is no statement of when to use this versus splunk_get_dashboard (single fetch), splunk_list_reports, or search-based discovery, and no stated prerequisites.

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