confluence_delete_page_property

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

Without any annotations, the description bears full responsibility for behavioral disclosure. It only states 'delete' but does not explain whether the property must exist, if the deletion is irreversible, or any side effects. The minimal description leaves significant uncertainty about behavior.

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 a single sentence of seven words, containing no fluff or redundant information. Every word is necessary and directly conveys the 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 simplicity of the tool (two parameters, no output schema), the description is still insufficient. It lacks details on error handling, whether the property is required to exist, and any impact on page data. A more complete description would note that the operation is permanent and provides no confirmation response.

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 input schema has 100% coverage with descriptions for both parameters, so the schema already explains what pageId and propertyId are. The tool description adds no additional semantic meaning beyond the schema, making it adequate but not enhanced.

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') and the resource ('a content property from a page'), which is specific and distinguishes it from sibling tools like deleting a page or creating/updating properties. This is a precise verb+resource pairing.

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?

No guidance is provided on when to use this tool versus alternatives such as confluence_delete_page, confluence_get_page_property, or other property tools. The description does not mention prerequisites, conditions, or when not to use it.

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