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

No annotations are supplied, so the description carries the full behavioral burden, yet it only implies destruction via the word "Delete." It says nothing about irreversibility, cascade effects on images/story items/videos/website links, required permissions, or failure behavior for a nonexistent id.

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 single short sentence is front-loaded and free of padding, but brevity here reflects under-specification rather than disciplined editing. Nothing extraneous, but almost nothing useful either.

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 destructive entity-level operation with no annotations, no output schema, and many similarly named delete siblings, this is far short of what an agent needs to invoke it safely and correctly. Scope, side effects, and post-condition are all undocumented.

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 100% for the single propertyId parameter, so the schema already documents it; the description adds no meaning beyond it. Baseline 3 applies when the schema does the heavy lifting.

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?

"Delete a property" states a verb and resource, which is better than a bare tautology, but it does not distinguish this from siblings such as property_delete_image, property_delete_story_item, property_delete_video, or website_property_delete. An agent cannot tell from the text whether this removes the entire property entity or only an association.

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?

There is no when-to-use, when-not-to-use, or prerequisite guidance at all. The crowded sibling namespace (multiple delete_* variants plus website_property_delete) makes the absence of routing guidance a real selection risk.

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