set_custom_property

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention side effects (e.g., overwriting existing custom properties), permissions, return values, or performance considerations. The description is entirely silent, providing no behavioral insight.

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 phrase, which is minimal, but it carries no useful information. This is under-specification rather than conciseness; the sentence does not earn its place as it adds zero value beyond the name.

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 0% parameter documentation, no annotations, and moderate operational complexity (setting a property on an object), the description is completely inadequate. Although an output schema exists, it does not compensate for the total lack of guidance on invocation or expected behavior.

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 schema has 3 parameters with no descriptions and 0% schema_description_coverage. The description adds nothing about the meaning or relationship of object_name, prop_name, and value. An agent has only the parameter names to infer semantics, which is inadequate.

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: set_custom_property' which merely restates the tool name with the server prefix. It provides no verb-resource clarity beyond the name itself and fails to differentiate from siblings like get_custom_properties or delete_custom_property. This is a tautology.

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 given on when to use this tool versus alternatives. The description does not mention prerequisites, expected workflow, or exclusions. An agent cannot infer when to choose this over get_custom_properties or delete_custom_property.

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