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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true; the description adds real value beyond them by spelling out what is not touched (data unchanged, commentary text preserved) and that cost/actions live in the app. It does not cover permissions or runtime/latency expectations, which keeps it short of a 5.

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 with the action, then the non-destructive guarantees, then the return value — a sensible ordering. The middle clause 'Nothing is deleted: the data is untouched, and text blocks (commentary) keep exactly what they say; people rewrite commentary in the app' repeats itself somewhat.

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 one-parameter, non-destructive refresh with no output schema, the description covers behavior, side-effect boundaries and the return value. The remaining gap is how to discover a valid dashboard_id, which list_dashboards presumably solves but is not mentioned.

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% for the single required dashboard_id parameter, and the description only implies it via 'of a dashboard' — it says nothing about format, where to get it, or that it must reference an existing dashboard. The implication is enough to function but adds little meaning over the schema.

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 — re-running every saved query of a dashboard and redrawing charts and numbers — which clearly separates it from list_dashboards, create_dashboard, query_rows and chart. An agent can identify the operation without opening the schema.

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 phrase 'exactly as saved' implies the tool is for replaying an existing dashboard rather than building or editing one, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative such as query_rows or list_dashboards.

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