delete_custom_property

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Delete', implying destructive action, but doesn't note that deletion is permanent, whether it requires specific permissions, what happens to dependent properties, or if the property must exist. This is insufficient for a mutation tool.

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 brief and front-loaded with the purpose. It includes an 'Args:' section, which is somewhat redundant for a single parameter but not harmful. It is appropriately sized for a simple tool, though minor structure improvements could be made.

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?

The description is minimal and does not address edge cases like non-existent property names, case sensitivity, or the effect on document integrity. It has an output schema (not shown), but that doesn't cover behavioral context. For a simple tool, it still lacks completeness in guiding the agent's expectations.

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%, meaning the description must explain parameters. It provides 'name: Property name to delete', which adds almost no value beyond the parameter name 'name' in the schema. It doesn't clarify format, validation rules, or constraints. The description fails to compensate for the lack of schema descriptions.

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 (custom document property). It specifies deletion 'by name', which directly corresponds to the required parameter. Among siblings like get_custom_properties and set_custom_property, the purpose is unambiguous.

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 like set_custom_property or delete_text. There is no mention of prerequisites, side effects, or contexts where deletion is appropriate. The agent receives no help in deciding between similar operations.

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