Delete Context By Query Parameters

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

The description adds significant behavioral context beyond annotations: it explains that deletion is permanent, removes associated layers/groups/markups, and mentions the API endpoint. Annotations provide destructiveHint=true, but the description reinforces and details the scope.

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 contains redundancy (e.g., 'This cannot be undone' appears twice, 'Permanently removes the specified Document Markup records' is repeated). While front-loaded with the main purpose, it could be more concise.

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 fully covers the tool's behavior, required parameters, optional parameters for special cases, and provides the API endpoint. No output schema, so return values are not needed. It is complete for an agent to select and invoke the tool.

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 description adds meaning beyond the input schema by grouping parameters for specific use cases (PIN deletion) and explaining the purpose of optional vs required parameters. Schema coverage is 100%, so baseline is 3, but the description provides extra guidance on when to use each parameter.

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 what the tool does: 'Delete a context and all its associated layers, groups, and markups.' It specifies the resource and action, and distinguishes from siblings by mentioning specific parameter usage for PIN deletion and optional parameters.

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 guidance on when to use specific parameters (e.g., for PIN deletion, pass sub_context_type and sub_context_type_id) and when to use skip_resource_deletion. However, it does not explicitly say when not to use this tool or mention alternative tools like delete_context_by_id.

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