Delete sources

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

The annotation destructiveHint: true already signals destructive behavior, and the description's 'Destructive' adds no extra context beyond that. It does not disclose irreversibility, required permissions, rate limits, or response behavior, so it adds minimal value beyond the annotation.

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 and front-loaded, but 'Destructive' is redundant because the annotation already says destructiveHint: true. It could have used that space for more valuable information.

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?

Despite being a simple tool with one parameter and no output schema, the description leaves out essential context: what 'sources' are, how to structure the batch input, what happens after deletion, and any prerequisite conditions. The annotation covers destructive intent, but the description is too sparse for an agent to reliably invoke the 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?

With 0% schema description coverage, the description was expected to explain the 'sources' parameter, but it only says 'Delete sources in batch.' It does not clarify that sources is an array of objects with id fields, nor what those ids refer to. The input schema exists but the description adds no semantic meaning.

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 sources in batch' clearly states the verb, resource, and scope, distinguishing it from the singular kommo_sources_delete tool. However, it could have explicitly named the sibling alternative for even clearer differentiation.

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 batch deletion tool versus kommo_sources_delete for single deletions. The description implies batch use but does not explicitly state alternate scenarios or exclusions.

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