Delete Surface Element

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

The annotations already declare destructiveHint=true and idempotentHint=false, so the core safety profile is known. The description adds meaningful cascade behavior: if pruneConnectors=true, connectors whose source or target referenced the deleted element are also deleted. That is a useful side effect beyond the annotations, though it omits concurrency and workspace-side effects covered by the schema.

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 two tightly written sentences with no waste. The primary action is front-loaded, followed immediately by the one important optional side-effect flag.

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?

With a full input schema, an output schema present, and annotations covering destructiveness and idempotency, the description supplies the main behavioral detail an agent needs: the pruneConnectors cascade. The concurrency semantics of expectedRevision are left to the schema, which is acceptable given full coverage.

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 all five parameters are already documented, including expectedRevision and workspaceId. The description mentions elementId and adds a behavioral explanation for pruneConnectors, but largely restates what the schema already says. Baseline 3 is appropriate.

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 states a specific verb and resource: 'Delete a surface element by id.' This clearly distinguishes it from sibling surface-element tools such as add_surface_element, list_surface_elements, and update_surface_element. However, it does not explicitly differentiate when to use delete_block or other deletion 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?

The description gives one conditional usage detail: set pruneConnectors=true to also remove referencing connectors. Beyond that, it does not explain when to choose this tool versus delete_block or update_surface_element, nor does it mention any preconditions or when-not-to-use guidance.

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