cancel_crawl_job_route

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), so the bar is lower. The description adds no additional behavioral context, such as whether cancellation is immediate, whether it requires the job to be active, or what happens on an already-cancelled job.

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?

At only two words, the description is concise but severely under-specified for a mutating tool with a required identifier. The dimension penalizes under-specification as much as verbosity, and this is too sparse to be useful.

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 non-idempotent, non-read-only action with a required crawl_job_id and no output schema, the description should at least clarify usage context or basic effects. It supplies no information beyond the title, leaving the agent relying entirely on annotations and the schema.

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 baseline is 3 even though the description says nothing about parameters. The schema itself contains the parameter description, though its wording ("to retrieve") is semantically off for a cancel operation.

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 "Cancel Crawl Job" is essentially a restatement of the tool name/title, making it a tautology rather than an elaboration. It does name the action and resource, but adds no differentiating detail beyond what the name already conveys.

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 when-to-use guidance is provided, nor are alternatives such as get_crawl_job_route or list_crawl_jobs_route mentioned. The implied usage is only that the tool cancels a crawl job, which an agent could already infer from the name.

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