Create Page

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

Annotations already indicate this is a write operation (readOnlyHint=false, destructiveHint=false). The description adds parameter-level details but does not disclose behavior such as return values, permission requirements, or error handling. With annotations present, the description is adequate but not rich.

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?

The description is concise: a one-line summary followed by a clear parameters list. Every sentence provides necessary information, no fluff. The structure is easily scannable for an agent.

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 the tool has 6 parameters and no output schema, the description covers all parameter semantics and the core purpose. It lacks mention of return values or error edge cases, but for a create operation with visible sibling context, this is a minor gap.

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 0%, so the description fully compensates by explaining every parameter: space_id, title, body_value, body_representation (with formats), parent_id (with root omission), and status (with defaults). This goes well beyond the minimal schema labels.

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 'Create a new page in a space', which is a specific verb+resource. This clearly distinguishes the tool from sibling tools like create_blogpost or create_space_property. The parameter list also reinforces the purpose.

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?

The description clearly implies when to use this tool (when creating a page in a space) but does not explicitly mention alternatives or exclusions. It does provide guidance on parameter choices (e.g., body_representation formats, parent_id for root placement), but no direct comparison to other create tools.

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