smartsuite_delete_dashboard

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

Annotations already indicate no read-only hint, but the description adds critical behavioral details: required permissions, destructive nature, inability to undo, and preview behavior when confirm is false. This provides transparency beyond annotations.

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 four sentences with no unnecessary words. Key information is front-loaded: the primary action comes first, followed by requirements, special cases, and warnings. Every sentence adds value.

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 simplicity of the tool and lack of output schema, the description covers prerequisites, parameter behavior, destructive nature, and constraints (refusing non-dashboards). It is sufficient for an agent to understand when and how to use the tool correctly.

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 coverage is 100%, so baseline is 3. The description adds meaning by explaining that confirm=true triggers permanent deletion while confirm=false returns a preview, and that dashboardId must refer to a dashboard report. This clarifies behavior beyond 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?

The description clearly states the action: 'Delete a dashboard and all its widgets.' It distinguishes from sibling tools by mentioning it refuses non-dashboard reports, and its focus on dashboards sets it apart from other delete tools (e.g., delete_records, delete_view).

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?

Explicit prerequisites are given (readwrite/admin mode, environment variables). The description explains the confirm parameter behavior and warns that the action is destructive and irreversible. It also notes that non-dashboard reports are refused, offering implicit guidance on valid inputs. However, it does not directly compare to sibling delete tools.

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