Delete semantic context

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

Adds substantial behavior beyond the annotations: requires the Creator role, ignores non-semantic node ids, refuses Tableau-managed contexts, succeeds without effect for nonexistent ids, and returns deleted name/statements for possible recreation. These details are consistent with destructiveHint=true, idempotentHint=true, and readOnlyHint=false.

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 front-loaded with 'WRITE', then moves efficiently through eligibility, return behavior, edge cases, and authorization. Every sentence adds operational value with no padding.

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 write tool, the description supplies the critical safety, authorization, eligibility, and idempotency context, while annotations and an output schema cover safety signals and return shape. The remaining gap is parameter-level detail, especially graph_id, which the schema also lacks.

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 0%, but the description does not explain the parameters. It refers generically to 'ids' and deleting an 'id', but never maps behavior to ctx_id or clarifies the optional graph_id at all, leaving both parameters semantically undocumented.

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?

States a specific write action and resource: delete a user-managed semantic context and its statements. It also scopes the operation by distinguishing user-created Tableau Knowledge contexts from Tableau-managed and non-context node ids, so an agent can identify the correct operation without opening the schema.

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?

Gives clear when/when-not guidance: only contexts created through Tableau Knowledge can be deleted, other node ids are ignored, and Tableau-managed SEMANTIC_CONTEXT_EXTERNAL contexts are refused. It does not name sibling alternatives such as update_semantic_context, but the eligibility rules are explicit.

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