Create Space Property

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

Annotations already indicate a non-read-only, non-idempotent operation. The description adds the unique key constraint ('must be unique within the space'), which is useful behavioral context not in the annotations. It doesn't fully explain error behavior if the key exists, but the annotations cover the main safety profile.

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 extremely concise, with a one-sentence purpose followed by a clean Args list. No wasted words; every part contributes to understanding the tool's function and parameters.

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 create operation with only three parameters and no nested structures, the description covers all necessary details: what it creates, each parameter's meaning, and the uniqueness constraint. It is complete for the tool's complexity.

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 schema provides no per-parameter descriptions (0% coverage), but the description compensates by fully explaining all three parameters: space_id, key with a uniqueness constraint, and value with allowed types (string, number, dict, or list). This adds significant meaning beyond the bare schema.

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 new content property on a space.' This specifies a distinct verb and resource, distinguishing it from sibling tools like create_page_property (which targets pages) and update_space_property (which modifies existing properties).

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 clearly indicates this is for creating a new property, which is implied by 'Create a new'. It doesn't explicitly mention when not to use it (e.g., for updating use update_space_property), but the create action is unambiguous and context is clear.

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