update-dashboard

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

The description only says 'Update,' but does not clarify whether it replaces all fields or merges, nor does it mention side effects, error handling, or authentication needs. Annotations (readOnlyHint=false, openWorldHint=true) partially cover mutation but the description should add more behavioral context.

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 extremely concise (5 words, one sentence), but it sacrifices meaningful detail. Still, it is efficiently short and front-loaded.

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?

With 7 parameters, 4 required, no output schema, and moderate complexity, the description is insufficient. It does not explain the update semantics (e.g., partial vs full replacement) or return value, leaving agents underinformed.

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%, so the schema already documents all parameters. The description adds no extra parameter-specific details, earning the baseline score of 3.

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 the verb (update) and resource (existing Datadog dashboard), distinguishing it from related tools like create-dashboard and delete-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 provides no guidance on when to use this tool versus alternatives, no prerequisites (like the dashboard must exist), and no exclusions.

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