plane-page-create

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

The description discloses that markdown is auto-converted to Plane-formatted HTML, which adds behavioral context beyond the schema. However, no annotations are provided, and the description does not cover permissions, idempotency, or failure modes.

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 two sentences, front-loaded with the core purpose, and no redundant information. Every word serves a purpose.

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 5 parameters and no output schema, the description is adequate but lacks return value information and guidance on when to use this tool versus sibling tools.

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%, so baseline is 3. The description adds marginal value by mentioning markdown default and optional content, but does not elaborate on parameter meanings beyond what the schema already provides.

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 it creates a new page with optional content, and specifies content formats (markdown or HTML) with auto-conversion. This distinguishes it from sibling tools like plane-page-update or plane-page-list.

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 indicates when to use the tool (to create a page), but does not explicitly mention alternatives or when not to use it. No guidance is given for choosing between this and related tools like plane-page-set-content.

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