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

With no annotations provided, the description carries the full burden of behavioral disclosure but provides none. It does not disclose whether the operation is idempotent, what happens if the parent_id doesn't exist, what the tool returns (page ID? full object?), or any side effects like notifications or permissions changes.

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?

While only three words long, this represents under-specification rather than effective conciseness. The single sentence fails to earn its place by providing only tautological information that duplicates the tool name, wasting the opportunity to front-load critical context about the page hierarchy or parent requirements.

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 tool with 5 parameters (including nested objects and conditional requirements), no annotations, and no output schema, the description is completely inadequate. It fails to explain the relationship between parent_type and parent_id, the requirement for properties when creating database pages, or the expected behavior of the created page in the system.

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?

The input schema has 100% description coverage, documenting all 5 parameters including the markdown format for content and the database/page enum for parent_type. The description adds no parameter semantics beyond the schema, but the schema is sufficiently descriptive to meet baseline expectations.

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 'Create a new page' is a tautology that restates the tool name (create_page). While it identifies the core verb and resource, it fails to distinguish from sibling tool 'create_database' or specify what kind of page system this operates within (implied by schema to be a database/page hierarchy but not stated explicitly).

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?

No guidance provided on when to use this tool versus alternatives like 'append_blocks' (when to create new vs. add to existing) or 'create_database'. No mention of prerequisites such as needing an existing parent page/database ID, or that 'properties' is required when parent_type is 'database'.

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