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

Annotations only say readOnlyHint=false and destructiveHint=false; the description goes well beyond them by disclosing merge semantics ("only the fields you send change"), creation-on-first-call with defaults, the authorization requirement (write scope), and the safety guarantee that autopilot is review-only and nothing sends without approval. Those are exactly the behavioral facts an agent needs before mutating a config.

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 short clauses, each load-bearing: what it does, how merging works, and the safety/auth constraints. The core action is front-loaded and there is no filler or repetition of schema detail.

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 six-optional-parameter mutation with thin annotations and no output schema, the description covers the essentials: upsert behavior, merge semantics, auth scope, and the review-only guarantee. It stops short of telling the agent how to inspect the resulting config (presumably get_autopilot_status) or what the call returns, a minor gap given no output schema exists.

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 per-field meaning is already documented and the baseline would be 3. The description adds real value above that baseline by clarifying that all six optional fields are patch-style partial updates rather than a full replacement, which changes how an agent should populate the payload.

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 precise verb pair and resource: "create or update the autopilot config," with the upsert semantics spelled out. The scope (autopilot config, not responder config, not a status read or a manual run) makes it easy to separate from siblings like configure_responder, get_autopilot_status, and run_autopilot_now without opening any schema.

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?

"First call creates the config with defaults" tells the agent it can call this with no prior setup, which is useful context for when to use it. However, there is no explicit exclusion or alternative named (e.g., use get_autopilot_status to read the current config, or run_autopilot_now to trigger a run), so the routing guidance is implied rather than stated.

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