delete_spread

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

No annotations are provided, and the description does not disclose any behavioral traits beyond the action. It fails to state whether the delete is irreversible, if it affects spread content, or any required permissions. The agent is left without critical context.

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 'Delete a spread' is extremely concise and front-loaded, meeting the conciseness goal. However, it is arguably too sparse, sacrificing completeness for brevity.

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?

The description is minimal given a simple tool with one parameter and no output schema or annotations. It does not explain implications like whether content is deleted or if the action is undoable, leaving the tool's full impact unclear.

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 100%, with the sole parameter 'spreadIndex' described as 'Spread index to delete'. The tool description adds no extra meaning beyond what the schema already provides. Baseline 3 applies per guidelines.

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 'Delete a spread' clearly states the action and resource, and the tool name itself includes the verb 'delete' and resource 'spread'. It distinguishes from siblings like 'delete_page' or 'delete_master_spread' by focusing on 'spread' explicitly.

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 guidance on when to use this tool versus alternatives (e.g., delete_page, delete_master_spread). There is no mention of prerequisites or conditions for use, leaving the agent to infer usage context.

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