delete-setting

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

No annotations are present, so the description must inform about behavioral traits. It fails to mention whether the deletion is permanent, requires special permissions, or has cascading effects. Additionally, the mention of 'configId' contradicts the schema, misleading about required parameters.

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, which is concise. However, it includes an inaccurate reference to 'configId', making it less reliable. Front-loading is okay but could be more precise.

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 simple tool with one parameter and no output schema, the description is brief but incomplete due to the inaccuracy. It doesn't explain return value or side effects, leaving significant gaps for agent decision-making.

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 100% coverage with a clear description for settingId. However, the description adds confusion by referencing a non-existent 'configId' parameter, which detracts from the schema's clarity. It does not enhance understanding of the existing 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 the action (removes) and the resource (Feature Flag or Setting). However, it incorrectly mentions a 'configId' parameter that doesn't exist in the schema, which could confuse an AI agent. Despite this, the core purpose is unambiguous.

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 update-setting, replace-setting, or other delete-* tools. Sibling tools are numerous, and without usage context, an agent may select the wrong tool.

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