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

Goes well beyond the annotations: it discloses that provider runs in progress are asked (not forcibly) to stop, that already-found results are retained (consistent with destructiveHint=false), and that the call reports settled/in-flight/unknown spend. It also pre-empts the idempotency question by stating repeat calls change nothing, matching idempotentHint=true.

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?

Four short clauses, each carrying distinct information (scope of stop, effect on provider runs, spend reporting, result retention, idempotency). Front-loaded with the action and no filler.

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?

Since there is no output schema, the description usefully explains what the call reports back, and it covers retention and idempotency for a mutation tool. Remaining gap is sourcing job_id and edge cases such as an unknown or already-completed job.

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 only 50% schema description coverage, the description should compensate, but it never mentions job_id or how to obtain it. The workspace parameter is documented in the schema (including the list_workspaces pointer), so the undocumented required parameter is the real gap.

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 ('Stop a research job') that is unambiguous against siblings like get_research_job and start_research_job. The following clauses immediately define what 'stop' concretely means, so the agent never has to guess the 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?

The description makes the effect clear ('nothing new is reserved or sent') and signals repeat calls are safe, but never names an alternative or a when-not condition. It does not mention checking status via get_research_job first, nor what to do if the job already finished — usage is only implied.

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