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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the safety bar is lower. The description adds only the pointer to the server instructions for the edit result and says nothing about what happens if kind or duration is omitted, or about the non-obvious fact that every edit mints a new timeline handle (which sits in the schema, not the description).

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?

Two short sentences with the action front-loaded and no padding. The second sentence is efficient but defers real information to an external document.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile of this mutation. For a five-parameter field-update tool with a defined result schema, the description supplies what is minimally required to invoke it correctly, though it is thin on optional-parameter behavior.

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 coverage is 40%, so the schema leaves gaps. The description names two of the five parameters (kind, duration) but never mentions preview, transition_id, or timeline_id semantics, and adds no format or constraint detail beyond the field names already implied by the schema.

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 and resource: change a transition's kind or duration. An agent can tell this edits an existing transition rather than adding (transition.add) or removing (transition.remove) one, though the distinction is inferred from the verb rather than stated.

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 explicit when-to-use or when-not guidance and no named alternative. The only signal is the implied notion that the transition must already exist, since the operation is a 'change' keyed on transition_id.

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