delete_configuration

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

No annotations provided, but the description fully discloses the safe nature of configuration deletion (pure metadata, no cascade), preconditions, and return value, ensuring the agent understands the behavior.

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?

Well-structured with front-loaded purpose, constraints, and use case. Slightly lengthy due to bilingual text, but each sentence adds value.

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 no output schema, the description explains the return value ('deleted configuration name') and covers all relevant aspects: purpose, preconditions, safety, and example use cases. Completeness is high for a simple deletion 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?

Only one parameter 'name' with schema coverage 0%, but the description clarifies 'The configuration to delete', which adds meaning beyond the schema title. Slightly lacking format details but sufficient for a single 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 'Delete a configuration from the active document' and explicitly distinguishes itself as the ONLY deletion tool in v1 MCP, unlike sibling tools that include other operations.

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?

Provides explicit use case (cleanup of obsolete trim variants) and prerequisites (configuration exists, not active, not only one), along with an alternative action (activate a different configuration first).

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