Delete a search job (primitive)

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

Discloses that deletion frees a slot and that deleting an already-gone job is not an error (idempotent). Annotations already indicate idempotentHint:true, but description adds vital context about the cap and cleanup practice.

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 efficient sentences with no wasted words. Purpose, usage guidance, and behavioral detail are all front-loaded.

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?

Given the tool's simplicity (one parameter, no output schema), the description fully explains its effect, idempotency, and proper usage context.

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?

Only one parameter 'id' with schema description 'Search job id.' Schema coverage is 100%, and description adds no further meaning beyond that already in the schema.

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 it deletes a search job and frees a slot against the 200-active-jobs cap. It distinguishes from siblings like sumo_create_search_job and sumo_get_search_job_status by being the delete operation.

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?

Explicitly advises to always delete jobs created via sumo_create_search_job or kept with keepJob:true. Provides context about the cap but does not explicitly mention when not to use.

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