edit_component_property

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

Discloses mutation (change), renaming side effect (new propertyId, old bindings intact), and return shape. Annotations already indicate non-readOnly/non-destructive, so description adds valuable behavioral context.

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?

Concise, well-structured, front-loaded with action. Every sentence adds value without redundancy.

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?

Covers all essential behaviors, side effects, and output shape despite no output schema. With 5 parameters and cross-referencing sibling tools, it's sufficiently complete.

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%, providing baseline 3. Description adds operational semantics: 'Supply at least one' and 'INSTANCE_SWAP only' for preferredValues, enhancing parameter understanding beyond schema.

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 tool changes an existing component property, specifying actions: rename, change defaultValue, or preferredValues (INSTANCE_SWAP only). It distinguishes from siblings like add_component_property and delete_component_property by focusing on editing.

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?

Provides guidance on supplying at least one parameter, notes renaming behavior, and directs to get_component_api for current IDs. Missing explicit when-not-to-use or alternatives, but generally clear.

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