Create Page

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

Annotations already declare readOnly=false and destructive=false, so the description correctly doesn't restate safety. It does add the crucial non-obvious trait that every call produces a new page (retries duplicate), plus what comes back (id and link). It omits permission/auth requirements, which keeps it from a 5.

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?

Three short sentences, front-loaded with what is created, followed by the return value and then the retry warning. Nothing is redundant and every sentence carries distinct information.

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 elaboration, annotations cover the safety profile, and all four parameters are documented. For a 4-param create tool, the description supplies the only thing structured fields can't: the non-idempotency warning and the routing to update_page.

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% and each parameter is already documented, including content as Markdown and parent_page_id for nesting. The description's "optionally under a parent page and with a Markdown body" merely paraphrases the schema, adding no format or constraint detail beyond it, so baseline 3 applies.

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 and resource ("Create a page in a space") plus the optional nesting and body format. It also names update_page as the sibling for the adjacent operation, so an agent can separate create from modify without opening schemas.

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?

Gives an explicit when-not-to-use rule ("do not repeat it to retry") and names the correct alternative for editing an existing page (update_page). That is the exact failure mode an agent hits with non-idempotent create tools.

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