compare_jobs

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety and idempotency profile is fully covered. The description adds the scope of what is compared (status, return code, failure indicators), but says nothing about behavior for missing jobs, mixed-environment comparison, or environment defaulting. Adequate but not rich, given annotations carry the main burden.

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?

A single front-loaded sentence with the compared fields enumerated immediately and no filler. Every clause earns its place.

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?

For a read-only comparison tool with a fully-documented schema and annotations covering safety and idempotency, the description says enough to call it correctly: which two IDs, optional environment, and what is compared. The only minor gap is how it behaves with invalid or cross-environment job IDs, which is not stated.

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 100%, so all three parameters (jobId1, jobId2, environment) are already documented in the schema, including the pointer to list_environments for the environment parameter. The description adds no format or syntax detail beyond the schema, so the baseline of 3 applies.

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 (compare) and resource (two jobs) plus the exact fields it reports on: status, return code, and failure indicators. This is clearly distinguishable from get_job_status or analyze_job_failure, which handle one job or failure analysis, not side-by-side diffing.

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 phrase 'side by side' implies the comparison use case, but there is no explicit guidance on when to prefer this over calling get_job_status twice, nor any mention of prerequisites or when not to use it. Usage must be inferred from the name and description alone.

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