Yandex Metrika: cancel job

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the bar is lower, yet the description adds real detail beyond them: temporary files are removed, and already finished files are not deleted, which is a meaningful scoping nuance an agent could not infer from annotations alone. The repeat-safety sentence largely restates idempotentHint.

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?

Three short sentences with the action front-loaded and no wasted wording. Slightly compressed to the point that the destruction scope could be tied more explicitly to what the caller loses.

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?

An output schema exists and annotations carry the safety profile, so the description only needs to convey the destructive scope, which it does. Only minor gaps remain, such as failure behavior for an already-completed job (implied by 'already finished files are not deleted').

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% and both parameters already carry descriptions naming their source tools (metrika_export_report, metrika_status). The description adds no parameter-level information, so the baseline 3 applies.

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?

States a specific verb and resource ('Cancels a Yandex Metrika export job') plus the secondary effect of removing temporary files, which distinguishes it from siblings like metrika_get_job and metrika_export_report. It does not explicitly name an alternative, but the job-cancel scope 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?

Implies usage context (cancelling an in-flight export) and notes 'Safe to repeat', but gives no explicit when-to-use/when-not guidance or pointer to sibling tools such as metrika_get_job for checking job state first. Adequate but with clear gaps.

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