delete_side_page

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It mentions the confirm:true requirement, which is a useful signal, but this is already present in the schema. It does not disclose that deletion is permanent, whether it cascades to side page versions, or any other side effects. For a destructive tool, this is insufficient.

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: two short sentences. 'Delete a side page' clearly states the action, and 'Pass confirm: true to proceed' adds the one critical instruction. No wasted words, and the key information is front-loaded.

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 tool with no annotations and no output schema, the description is under-specified. It lacks critical context such as permanence, effect on versions (especially since a sibling delete_side_page_version exists), and any post-deletion consequences. The description is insufficient to fully inform an agent about the tool's impact.

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%, so the baseline is 3. The description only repeats the confirm requirement already described in the schema ('Must be true to confirm deletion') and adds no additional meaning for slug or sideKey beyond their schema descriptions. No new parameter semantics are provided.

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 uses the specific verb 'Delete' and the resource 'side page', making the tool's purpose immediately clear. It distinguishes from sibling tools like edit_side_page, view_side_page, and delete_side_page_version by indicating it deletes the entire side page rather than a version or property.

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. Sibling tools include delete_side_page_version and restore_side_page_version, and the description does not clarify that this tool is for permanently deleting the entire page, nor does it mention any prerequisites or contexts (e.g., unpublishing first). This leaves the agent without explicit selection criteria.

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