list_dashboard_snapshots

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

With no annotations, the description carries the full burden of behavioral disclosure. It states snapshots are 'locally saved' and 'captured before mutations,' hinting at a safe, read-only operation, but it does not clarify authorization needs, side effects, or data freshness. The minimal information leaves significant behavioral ambiguity.

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 a single concise sentence, but it sacrifices essential detail for brevity. While there is no fluff, the structure fails to front-load key information such as parameter usage or result behavior. The conciseness is acceptable but comes at the cost of completeness.

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?

Given the tool has 2 parameters, no annotations, and an output schema, the description should provide more context. It lacks explanations of parameter roles, usage scenarios, and behavioral traits. The presence of an output schema mitigates return-value documentation, but the description remains incomplete for effective use.

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%, requiring the description to explain parameter meanings. However, the description does not mention dashboard_id or limit. Without any parameter semantics, the agent cannot infer how to filter or paginate results, making the tool nearly unusable.

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 tool lists 'locally saved dashboard snapshots captured before mutations.' It identifies the resource (dashboard snapshots) and the action (list). While it distinguishes from sibling tools like list_dashboards, the phrase 'captured before mutations' may be ambiguous without additional context.

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?

No explicit guidance is provided on when to use this tool versus alternatives. Sibling tools like restore_dashboard_snapshot exist for restoring snapshots, but the description does not clarify when listing is appropriate. This omission limits the agent's ability to choose correctly.

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