create_page

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

No annotations are present, so the description carries the full behavioral disclosure burden. It identifies the action as creating a new page but does not mention permissions, side effects, return values, error behavior, or whether creating could overwrite an existing note_code. This is minimal for a write operation.

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 convey the action, the resource, and the key constraints without wasted words. The required parameters are stated up front, and the optional folder_id behavior follows naturally.

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 essential action and required parameters, and the schema fully documents all six parameters. However, with no output schema and no annotations, it omits the expected result of the creation, how errors are surfaced, and any permission requirements, leaving the tool partially underspecified.

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 even without additional parameter detail. The description restates that note_code and title are required and adds that folder_id is optional, but these facts are already present in the schema, adding little net value.

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 a new page in NotePM.' It also clarifies the required fields, making the tool's purpose immediately clear and distinguishing it from update_page and create_tag.

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 implies when to use the tool by saying 'Create a new page', but it does not explicitly mention alternatives or when not to use it. There is no guidance about preferring update_page for existing pages or search_pages for retrieval.

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