lakeview_dashboard_purge

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description confirms permanent deletion, which is consistent. However, it does not add any behavioral context beyond what annotations provide, such as irreversibility or authorization requirements.

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 sentence that is clear and to the point, with no unnecessary words. It fits the minimal structure appropriate for a simple tool.

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's simplicity (1 parameter, schema coverage 100%, annotations present, output schema exists), the description sufficiently conveys the core functionality. It could mention the irreversible nature, but the annotations and parameter description cover the key aspects.

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?

The schema description coverage is 100% for the single parameter, with the parameter description specifying it must be a trashed dashboard ID. The tool description does not add further meaning beyond what the schema already provides.

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 action: permanently delete a trashed Lakeview dashboard. It specifies the verb (permanently delete) and resource (trashed Lakeview dashboard), distinguishing it from siblings like lakeview_dashboard_delete (which likely moves to trash) and lakeview_dashboard_restore (which restores from trash).

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 explicit guidance on when to use this tool versus alternatives like lakeview_dashboard_delete or lakeview_dashboard_restore. It implies the dashboard must already be trashed, but does not state when to use this tool instead of others.

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