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

Adds real value beyond the annotations: it discloses that already-delivered research may remain billable and that terminal/unknown jobs error out rather than silently succeeding. It does not say whether partial results are retained or whether the cancel is reversible, but the destructiveHint already flags the irreversible-write profile.

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, each doing distinct work: scope, billing consequence, error behavior. The most important constraint (queued/running only) is 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?

With no output schema, the description does cover the success/failure outcomes and billing side effect well. However, for a destructive single-parameter tool it leaves the caller without any hint on sourcing the jobId or verifying job state beforehand, which is a meaningful gap.

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 0% and the single parameter (jobId) is never mentioned in the description — no explanation of where to obtain the ID or what the 'owned' qualifier means for validity. The pattern constraint lives only in the schema, leaving the description to carry the burden and not doing so.

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 ('Cancel') and resource ('an owned search') plus a state constraint ('still queued or running'), which tells an agent exactly which jobs this applies to. It does not name the relevant sibling (get_search_status) as the way to confirm that state, so differentiation is implied rather than explicit.

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?

Gives a clear usage condition (only for queued/running owned searches) and the failure mode (terminal or unknown job returns an error), which effectively defines when not to use it. It stops short of recommending a status check via get_search_status first, which would be the natural pre-flight guidance.

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