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

Beyond annotations, the description discloses that the page is published on creation, that a creator can only have one page, and that the page shows the creator's profile avatar. These are meaningful operational expectations not present in the schema or 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?

Four dense sentences with no filler: purpose, constraint, parameter guidance, and follow-up workflow are each covered. Information is front-loaded and every sentence 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?

The description covers the one-page constraint, slug behavior, publication state, and subsequent tool usage. Since there is no output schema, a note about the return value would improve completeness, but this is a minor gap for a create tool whose parameters are fully documented.

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 100%, so the baseline is 3. The description adds extra meaning by explaining that slug is unique and lowercased, that omitting it derives one from the name, and that preferred slugs can be pre-checked with split_check_slug.

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: 'Create the creator's SplitPage — their public page at split.co/splitpages/<slug>'. It also differentiates from siblings by noting the one-page constraint and pointing to split_update_page for existing pages.

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 gives when-to-use and alternatives: it 'refuses when one already exists (use split_update_page)', suggests checking a preferred slug with split_check_slug, and routes follow-up work to split_create_section and split_create_collection. No inference is required.

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