Delete source

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

The description repeats the 'Destructive' trait already declared by the destructiveHint annotation, without adding extra context such as irreversibility, cascading effects, or permission requirements. With annotations present, the bar is lower, but the description fails to provide any added behavioral insight beyond what annotations already convey.

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, front-loaded sentence with no waste. 'Delete a source by ID' is direct, and the redundant word 'Destructive' is brief and not verbose. Every word serves the purpose of conveying the operation.

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 one-parameter destructive tool, the description combined with annotations is nearly complete. It specifies the action and destructive nature, though it could mention irreversibility or impact on related data. Given the tool's simplicity and annotation coverage, it is sufficiently complete, just not exhaustive.

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 schema has zero description coverage for the 'id' parameter, and the description only mentions 'by ID' without elaborating on the parameter's semantics, format, or source. It adds minimal value over the schema, insufficient to compensate for the 0% coverage 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 'Delete a source by ID' clearly states a specific verb (delete), resource (source), and the parameter (ID). It distinguishes from sibling tools like kommo_sources_delete_many by specifying single-ID deletion, making the tool's purpose immediately 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?

The description clearly implies use when deleting a single source by its ID, and the inclusion of 'by ID' implicitly contrasts with delete_many. However, it does not explicitly state alternatives or when not to use, lacking a direct exclusion or alternative reference.

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