Create page

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds context about section resolution (by name, no lookup) and default section behavior, but doesn't disclose return values or error conditions. This adds some value beyond annotations without being 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?

Two sentences, front-loaded with the core purpose, and no redundant wording. Every sentence adds meaningful guidance.

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?

For a create operation with annotations and full schema coverage, the description covers the essential behavioral details (section by name, default omission). It doesn't explain return values or failure modes, but those are not expected given the presence of annotations and a relatively simple input schema.

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 covers all parameters at 100%. The description adds value by specifying 'Pass the section by NAME' and that section can be omitted if a default is configured, clarifying the intended usage of the section parameter beyond the schema's 'name, path, or ID'.

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 'Create a new page' with a specific verb and resource, distinguishing it from sibling tools like createSection and appendToPage. It also adds clarifying details about section handling.

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?

Provides actionable guidance: pass section by NAME, no lookup needed, and omit if default exists. This tells the agent when and how to use the tool, though it doesn't explicitly contrast with appendToPage or other alternatives.

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