tm_resume_run

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

Annotations already indicate destructive (destructiveHint=true) and non-idempotent (idempotentHint=false) behavior. The description adds specific context: continuation from RPS curve position and SEQUENTIAL variable-set cursors, and clarifies non-idempotency in the no-state case, which adds value beyond annotations.

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?

The description is front-loaded with the main action and adds necessary details in a few concise sentences. Minor improvement could be to combine sentences for even tighter structure.

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?

The description covers purpose and behavior well for a simple tool with one parameter and no output schema, but it lacks parameter explanation and any indication of return values or side effects beyond continuation.

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?

There is one required parameter 'profile_id' with no description in the schema (0% coverage). The description does not explain this parameter, leaving ambiguity about its purpose (e.g., run ID vs profile ID).

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 the action 'Resume a paused run' and the resource, distinguishing it from sibling tools like stop/pause by mentioning continuation from pre-pause position.

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 explicitly compares with stop/pause, warns that calling resume without an in-flight or paused run results in a 400 error, and implies the tool is for resuming previously paused runs.

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