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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe read operation. The description adds the schema diff summary and composition error context, which adds value beyond annotations but doesn't go deep into behavioral detail. Given strong annotations carry the safety burden, a 3 is appropriate.

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 dense sentences with zero wasted words. The first sentence states purpose and deliverables, the second gives usage context with a concrete example, and the third lists required inputs. Highly efficient and 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?

The tool has an output schema, so return values are presumably documented there. With strong annotations, an output schema, and a rich description covering what fields are returned, when to use it, and what inputs are needed, this is largely complete. Minor gap: it doesn't clarify what 'schema diff summary' entails or whether the launch history tool's ids differ in format, but the output schema likely covers return structure.

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 compensate for parameter meaning. The description says 'Provide the graph ID, variant name, and launch ID' which names the parameters, but adds no additional semantics beyond what the schema property names (graphId, variant, launchId) already convey. It doesn't explain formats, sources, or relationships between parameters, and there's a slight mismatch ('variant name' vs. 'variant').

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 tool inspects a single launch by ID, enumerating the specific detail fields (status, timestamps, subgraph changes, errors, schema diff). It strongly distinguishes from siblings like GetLaunchHistory (list) and GetLatestLaunch (single but latest), making the purpose unmistakable and non-tautological.

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?

Provides explicit when-to-use guidance: 'Use to drill into a specific launch — e.g. a failed or superseded one found via GetLaunchHistory (pass its id here).' It names the alternative tool and explains how the history tool feeds into this one. Also lists required identifying parameters (graph ID, variant, launch ID). This is model usage guidance.

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