Delete Page Property

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

Annotations already declare destructiveHint=true, so the destructive nature is covered. However, the description adds no behavioral context beyond the bare 'Delete', such as whether deletion is permanent, reversible, or requires special permissions. It does not contradict annotations but also does not enrich them.

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 concise with a single declarative sentence and a simple Args list. It is easy to scan, but the Args list is redundant with the input schema, so some elements could be trimmed without loss.

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 deletion tool with annotations covering destructiveness, the description is minimally viable. However, it lacks any mention of edge cases, effect on related data, or success/failure behavior, which would make it more complete for an agent.

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 merely repeats the schema field names ('page_id', 'property_id') and their types ('Page ID', 'Property ID'), adding no additional meaning. The schema already provides these titles, so the description fails to compensate for the lack of semantic detail.

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 'Delete a content property from a page' with a specific verb and resource. It distinguishes from sibling tools like delete_page, delete_blogpost, and delete_attachment by targeting content properties specifically.

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 such as update_page_property or delete_page. There are no explicit exclusions or context about prerequisites, making the usage context implied rather than stated.

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