Delete Context

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is known. The description adds only the word 'permanently', which is essentially redundant with destructiveHint. It does not disclose any additional behavioral details such as side effects on associated resources, permission requirements, or irreversibility beyond what the annotation implies.

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 a single, front-loaded sentence: 'Permanently delete a context by id.' It contains zero wasted words, clearly conveys the action, and is easily parsable for an AI agent.

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?

This is a simple single-parameter destructive tool with clear annotations. No output schema exists, but for a delete operation the response semantics are often straightforward. The description covers the essential purpose and permanence, and the sibling tools provide surrounding context. It is complete enough for the tool's complexity, though it could have mentioned expected response behavior.

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 schema provides 100% coverage with a clear description for context_id ('Context id'), so the schema carries the heavy lifting. The description merely restates 'by id' without adding any new semantic detail about the parameter's format, source, or usage. 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 uses a specific verb 'delete' with a clear resource 'context' and the exact identifier ('by id'). It clearly distinguishes from sibling tools like create, update, list, and get contexts, making the tool's purpose unmistakable.

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 implies when to use the tool (when you have a context_id and need to delete it), but it does not explicitly mention alternatives or exclusions. No guidance is given on when not to use it (e.g., versus updating or deactivating), but the simple nature of the operation makes the context reasonably clear.

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