Delete Space Property

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

Annotations already provide destructiveHint=true and readOnlyHint=false, so the tool's destructive nature is known. The description adds no additional behavioral context such as irreversibility, cascading effects, or required permissions. It only restates the action, which is already implied by the annotations and tool name.

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 concise, front-loaded with the main action, and includes a clear argument list. No unnecessary words or repetition.

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 two-parameter delete operation, the description is largely complete. It explains the parameters, and the annotations cover the destructive and idempotent nature. However, it does not mention return values or side effects, but given the lack of an output schema and the simplicity of the tool, this is acceptable.

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 0%, but the description includes an 'Args' section explaining each parameter: 'space_id: The ID of the space' and 'property_id: The ID of the property to delete.' This adds meaning beyond the bare schema by clarifying the role of each parameter, especially that property_id is the one to delete.

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 ('Delete a content property from a space') with specific verbs and resource. It distinguishes itself from sibling tools like delete_page_property or update_space_property by clearly naming the target resource.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, conditions, or alternative tools such as update_space_property or create_space_property. This is a clear lack of usage context.

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