split

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

Discloses destructive nature ('Destructive: creates multiple output files') beyond the destructiveHint annotation. Details dry-run capability, overwrite protection, and return format (JSON with file list and record counts). No contradictions with annotations.

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?

Five sentences, each adding value. Front-loaded with purpose, then key behaviors, output info, and usage guidance. No fluff.

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?

Given 9 parameters, full schema coverage, no output schema, and destructiveHint annotation, the description covers purpose, default behavior, safety features, output format, and alternatives. Sufficient for agent decision-making.

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 100%, so baseline is 3. The description adds minimal new info beyond schema defaults (e.g., default line count, prefix) but does not significantly enhance understanding of individual parameters. It repeats some defaults already in 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?

The description clearly states the tool's purpose: 'Split input into chunked output files by line count or byte size'. It specifies the verb (split), resource (input), and primary methods (line count or byte size), distinguishing it from content-based splitting tools like csplit.

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?

Explicitly explains when to use (partitioning large datasets) and when not to use (content-based splitting, directing to csplit). Provides default behavior (1000 lines per chunk) and mentions dry-run and overwrite protection. Includes alternative tool reference ('csplit').

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