Create Page Property

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

The description adds the useful constraint that the key must be unique on the page, which gives some behavioral context. Annotations already indicate this is not read-only and not destructive, so the safety profile is partially covered. However, the description does not disclose what happens if the key already exists, what the return value is, or any other side effects, leaving a moderate transparency gap.

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 very compact, front-loaded with the purpose, and follows a clean 'Args' structure without any wasted words. Every sentence adds value.

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 simple three-parameter tool with no output schema, the description is nearly complete: it covers purpose, parameter meanings, and a key constraint. The only notable omission is the return value or error behavior, which would improve completeness, but the current level is adequate for the tool's simplicity.

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?

With 0% schema description coverage, the description compensates well by providing concise, meaningful explanations for all three parameters: page_id, key (with uniqueness note), and value (any JSON-serializable value). This is valuable beyond the bare schema and clarifies the intended use of each argument.

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 the action ('Create a content property on a page'), naming both the operation and the resource. It distinguishes itself from sibling tools like update_page_property and delete_page_property by its explicit 'create' verb and 'on a page' scoping, which also separates it from create_space_property.

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?

There is no explicit guidance on when to use this tool versus alternatives such as update_page_property or delete_page_property. The context is clear (creating a new property) but no exclusions or comparisons are provided. This falls short of helpful usage guidelines.

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