delete_custom_property

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals nothing about the operation — e.g., whether missing properties raise errors, whether deletion is irreversible, or what the return value indicates. The only hint is the word 'delete' in the name, which implies mutation but adds no detail.

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 short sentence, but its brevity is a result of under-specification rather than efficient communication. It contains no usable information beyond the tool name, so it fails to earn its place as a substantive description.

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 tool, the name and parameter labels give some surface-level context, but the description omits any behavioral or error-handling details. An agent cannot infer what happens on failure, whether the property must exist, or what the output schema returns — gaps that a brief description could easily fill even without annotations.

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%, and the description does not explain either parameter (object_name, prop_name). While the parameter names are somewhat self-explanatory, the description adds no value beyond what the raw schema field names already imply, leaving the agent to guess at types, formats, or constraints.

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 is 'Blender Studio Pro MCP: delete_custom_property' — a direct restatement of the tool name with a prefix. It does not state what the tool does (e.g., 'Deletes a custom property from an object'), so it fails to add any clarifying meaning beyond the name itself.

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 guidance on when to use this tool versus alternatives. Sibling tools like set_custom_property and get_custom_properties exist, but the description doesn't mention them or any conditions that would select delete over them. The omission is a neutral lack of guidance rather than active misinformation.

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