agileconfig_delete_config

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

The description mentions '软删除' (soft delete), which adds behavioral context beyond the schema (which only says 'delete'), indicating the operation is reversible. However, with no annotations provided, the description does not disclose other important traits like required permissions, side effects, or return behavior, so it only partially meets the transparency burden.

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 extremely concise (one phrase), conveying the core purpose and a key behavioral trait ('soft delete') without unnecessary words. It is well front-loaded, though a slightly more structured sentence could improve readability without sacrificing brevity.

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 deletion tool with no output schema and no annotations, the description should cover more behavioral context, such as what the tool returns, whether cascading deletes occur, or the impact on dependent data. It only mentions 'soft delete', leaving significant gaps for the agent.

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?

Schema description coverage is 100%, so the schema already documents both parameters. The description does not add any additional meaning or constraints beyond what the schema provides (e.g., id format, env behavior), so no value is added beyond the baseline.

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 ('specified configuration item'), with the additional qualifier of 'soft delete' which distinguishes it from a hard delete. Among siblings like 'agileconfig_create_config' and 'agileconfig_update_config', this tool's 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, such as 'agileconfig_delete_app' or 'agileconfig_delete_node'. There is no mention of context, preconditions, or exclusions, 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.