smartsuite_delete_view

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

Beyond annotations (readOnlyHint=false), the description reveals destructive nature ('cannot be undone'), the two-step deletion process (preview vs. permanent), and special refusal cases. No contradiction with 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 a single paragraph but is concise and well-structured. Every sentence adds necessary information, with prerequisites front-loaded and no redundancy.

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 (2 params, no output schema), the description covers all essential aspects: action, prerequisites, limitations, behavior, and destructive nature. It is complete for its complexity.

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% with descriptions for both parameters. The description adds value for confirm by explaining its dry-run vs. permanent behavior, going beyond the schema description. For viewId, it restates 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 'Delete a view (report)', using a specific verb and resource. It also distinguishes from siblings by noting that forms and dashboards have their own tools.

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, SMARTSUITE_ENABLE_SCHEMA_WRITE=true, SMARTSUITE_ENABLE_DELETE=true). It explains when not to use (refuses last view, forms/dashboards) and provides alternatives. The confirm parameter behavior is also clearly described.

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