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

Annotations already declare readOnlyHint=false, openWorldHint=false and destructiveHint=false, so the agent knows this is a non-destructive local-side-effect operation. The description adds almost nothing beyond that: it doesn't say whether the run is synchronous or job-based, whether it writes output to the project, or whether the document is modified. With annotations carrying the safety profile, this still leaves meaningful behavioral gaps.

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?

A single front-loaded sentence with zero redundant or filler text; the action and target come first. It is appropriately sized for a one-line description, though the brevity borders on under-specification rather than wasteful padding.

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. But for a write-flagged operation with 4 parameters (two required) and a 25% documented schema, the description omits prerequisites (publishing/version), execution model (async job vs. inline result), and effect on the document or project — leaving an agent unable to invoke it confidently.

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 only 25% (only project_slug is documented), and the description supplies no parameter meaning at all — it doesn't explain splitter_id, document_id, or version (e.g., which splitter version is targeted). 'In this project' only loosely gestures at project scoping and does not compensate for the coverage gap.

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 ('Run') and resource ('published fixed page-range splitter on a document'), which lets an agent distinguish it from splitters.test_page_range and splitters.create_page_range by the 'published' qualifier. However, it never names the sibling tools or explicitly contrasts running vs. testing vs. creating, so differentiation is inferred 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 when-to-use guidance, no prerequisites, and no alternatives are given. The word 'published' hints that a splitter must be published first (via splitters.publish), but this precondition is never stated, nor is it explained when to use this versus test_page_range.

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