config_config_drop

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

The description only says 'Delete an entire named config store' without detailing irreversible consequences, required permissions, or side effects. Given no annotations, the description carries full burden but fails to disclose behavioral traits.

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 concise sentence with a category prefix. It is front-loaded and to the point, though it could include more useful context without being verbose.

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 is a mutation that deletes an entire config store, the description lacks crucial context about risks, rollback options, and expected output. With an output schema present but not described, the description does not adequately prepare an agent for usage.

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?

With 0% schema description coverage and one parameter 'name', the description does not add meaning beyond the schema. It doesn't clarify what 'name' expects, e.g., must match an existing store. Baseline would be 3 if coverage were higher, but here it's low and description doesn't compensate.

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 the resource (entire named config store), distinguishing it from sibling tools like config_config_delete which likely deletes a specific key. It is specific and 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 on when to use this tool versus alternatives such as config_config_delete for individual keys. No prerequisites, consequences, or context provided.

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