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

With no annotations, the description carries the burden and does disclose the key side effect: subsequent items on the same track are rippled, not just the target. It also discloses the failure mode. However, it says nothing about whether the operation is undoable (project.undo exists), what 'expectedVersion' does on mismatch, or what happens on other tracks.

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 sentences, zero filler, with the ripple scope front-loaded and the failure condition second. 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 mutation tool with no annotations, no output schema, and 0% parameter documentation, the description covers the core behavior and one failure mode but leaves versioning semantics, permission requirements, and return/undo behavior unexplained. It is adequate to understand the intent but not to invoke confidently in a versioned editing flow.

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 three undocumented parameters. It only conveys the item concept; 'projectId' and especially 'expectedVersion' (clearly an optimistic-concurrency token) are never explained, leaving a required integer parameter with no stated meaning or failure behavior.

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 states a specific verb ('Ripple ... earlier') and resource ('a timeline item ... on the same track'), and the singular 'a timeline item' implicitly separates it from the sibling timeline.close_gaps. It never names that sibling explicitly, so an agent must infer the singular/plural distinction rather than read it.

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?

It provides a useful precondition-style exclusion ('Fails if there is no gap before the item'), which tells the agent when the call will not work. It gives no guidance on choosing between this, timeline.close_gaps, timeline.move_item, or timeline.trim_item, so usage selection is only implied.

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