Delete Dynamic Tool

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

With no annotations, the description must disclose behavioral traits. While 'delete' and 'unregister' imply a destructive action, the description omits details such as required permissions, irreversibility, cascading effects, or whether the tool must be disabled first. It adds minimal value beyond the tool's name.

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 sentence, making it brief and front-loaded. However, its brevity leads to under-specification; it does not earn its place because it omits important information that could be included concisely.

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?

Given the tool has three parameters, no annotations, and no output schema, the description should provide more context. It fails to cover parameter meanings, side effects, auth requirements, or typical usage flow, making it incomplete for effective agent invocation.

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 input schema has three parameters (adminToken, name, expectedRevision) but zero description coverage. The tool description fails to explain any parameter purpose, meaning of expectedRevision (concurrency control?), or why adminToken is not required. This is a critical gap.

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 the action ('Delete') and resource ('dynamic tool'), and adds 'unregister it from MCP' to specify the effect. It is distinguishable from sibling tools like 'create' or 'enable', though it could be more explicit about whether it also disables or cleans up related resources.

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 like 'disable' or 'update'. The description does not mention prerequisites, authorization, or scenarios for deletion, leaving the agent to infer usage from the name alone.

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