restart_job_with_sampling

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

With no annotations, the description must disclose behavioral traits. It only says 'restart', but does not explain side effects (e.g., job state loss, whether it stops then starts, or updates configuration). Vague term 'proper sampling configuration' lacks specifics.

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 a single 10-word sentence, front-loaded with the core purpose. Every word serves a purpose; no redundancy or 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?

Despite having an output schema, the description omits return value expectations, error conditions, permissions, and side effects. Given the tool's complexity (mutating a job) and lack of annotations, the description is incomplete.

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%, so the description must add meaning. It mentions 'new SQL' and 'sampling configuration', providing high-level context for the parameters. However, it does not detail each parameter (e.g., sample_interval units or sample_all_messages behavior), leaving gaps.

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 that the tool restarts a job with new SQL and sampling configuration, specifying the verb and resource. It distinguishes from siblings like 'execute_job' or 'configure_sampling' by combining restart with sampling updates, though it could be more precise about what 'proper' means.

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 guidance on when to use this tool versus alternatives like stopping and restarting manually or using 'execute_job'. No prerequisites, exclusions, or context for job state requirements are provided.

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