Update Space Property

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

Annotations already indicate this is a write operation (readOnlyHint=false) and non-destructive. The description adds meaningful context by noting that version_number is 'incremented automatically', suggesting optimistic concurrency behavior. No contradiction with annotations.

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 one clear introductory sentence followed by a structured Args list. Every line serves a purpose with no fluff, making it easy to parse and front-loaded with the primary action.

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?

With 5 required parameters and no output schema, the description covers the basics but omits potential side effects or behavior on version conflicts. The openWorldHint=true annotation suggests unforeseen effects that are not addressed, leaving some gaps for an update operation.

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 0%, so the description's Args list compensates by explaining each parameter. It clarifies that value is the 'New property value' and version_number is the 'Current version number', adding meaning beyond the schema's bare titles. Some descriptions like 'key: Property key' are tautological but overall helpful.

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 'Update an existing content property on a space', which specifies the verb (update) and resource (content property on a space). It distinguishes from sibling tools like create_space_property, delete_space_property, and get_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?

The description implies usage for updating existing properties but does not explicitly state when to use this tool versus alternatives like create_space_property or delete_space_property. No exclusions or alternative recommendations are provided.

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