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

Annotations already declare this is a non-read-only, destructive mutation, so the safety profile is covered. The description adds genuinely useful context beyond that: the optimistic-concurrency requirement that expected_draft_revision must match the current revision. It still omits whether this operates only on drafts, permission requirements, and what the update overwrites.

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 tight, front-loaded sentences with no waste, and the concurrency constraint is stated directly. It is efficient, though sentence two could have absorbed a bit more of the config semantics at little cost.

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 no explanation, but the tool has 6 parameters with a deeply nested config object and a 17% coverage schema. The description leaves the entire config structure, the mode constraint, and the draft-only scope unexplained, which is inadequate for this complexity.

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 only 17%, so the description must carry the burden, but it only explains expected_draft_revision (the concurrency check). The complex nested config (mode const "logical", sectionTypes, routingMode, thresholds), name, description, and splitter_id receive no explanation in the description.

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 and resource ("Updates a logical splitter draft"), and the word "logical" implicitly separates it from the sibling update_page_range. It is clear, though it never explicitly names that sibling or what distinguishes the two flows.

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?

There is no guidance on when to use this versus splitters.create_logical, splitters.publish, or splitters.update_page_range, and no mention of the draft-vs-published workflow. The agent must infer all routing from the name alone.

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