splunk_create_dashboard

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

With no annotations, the description carries the full burden. It discloses the write-mode requirement and that the payload may be either Simple XML or Dashboard Studio JSON, which is genuinely useful. It does not say whether a duplicate 'name' overwrites or errors, nor anything about permissions beyond write mode, so key mutation risk remains undisclosed.

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?

Front-loaded purpose sentence followed by a compact Args block; no filler. The small cost is that the Args block is the only structural element and the purpose line does not preview the prerequisite prominently.

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 explained. But for a mutation tool with zero annotations, the definition omits collision/overwrite behavior and error conditions an agent should anticipate before calling.

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 description must compensate, and it does: it clarifies 'name' is a unique view ID, 'label' is the display title, 'app' defaults to 'search', and critically that 'xml_data' accepts either XML or JSON despite its name. Minor remaining ambiguity (how label behaves on duplicate, whether xml_data is validated) keeps it from a 5.

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 ('Create a new Simple XML or Dashboard Studio dashboard'), which clearly separates it from sibling mutators like splunk_update_dashboard and splunk_delete_dashboard. It does not explicitly name those siblings, so it stops short of full differentiation.

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 parenthetical '(requires write mode)' gives a real prerequisite, which is useful gating information. However, there is no guidance on when to create vs. update an existing dashboard, or what to do if the name already exists.

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