delete_master_spread

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

The description simply states the action with no disclosure of behavioral traits. Since no annotations are provided, the description should convey whether the deletion is reversible, what items are affected, or any side effects. It fails to do so.

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 extremely concise but lacks structure. It is a single sentence that conveys the purpose, but its brevity may sacrifice clarity and scanability.

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 destructive action with no output schema and no annotations, the description is incomplete. It does not explain the impact of deletion (e.g., whether master items are removed), nor does it address potential prerequisites or constraints.

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 input schema provides a description for the only parameter 'name', achieving 100% coverage. The tool description adds no additional semantic meaning beyond what the schema already states.

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') and the resource ('master spread'), which distinguishes it from sibling tools like create_master_spread or get_master_spread_info. However, it is minimal and lacks any scope or qualification.

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 guidance is provided on when to use this tool versus alternatives, such as delete_spread or delete_page_item. There are no prerequisites, exclusions, or context about expected usage scenarios.

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