bind_component_property

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

With no annotations, the description carries the full burden. It implies a mutation of node/component state but says nothing about required permissions, whether the binding is reversible, what the 'unbind' path does, or what happens to existing references. Only the operation type is disclosed.

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?

A single front-loaded sentence with zero filler. Nothing in it is wasted, and the core action leads.

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 5-parameter mutation tool with no annotations, no output schema, and no per-parameter documentation, the description is too thin. It should at least explain the required vs optional params and the bind/unbind semantics.

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% across 5 parameters, so the description must compensate and largely does not. It gestures at the property types and the node-field concept, but leaves nodeId, propertyOwnerId, propertyName, and unbind unexplained beyond their names.

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?

States a specific verb (bind) plus the resource (component property) and target (node field), and names the property kinds BOOLEAN/TEXT/INSTANCE_SWAP. This differentiates it from sibling bind_variable_to_property, but the trailing 'using componentPropertyReferences' is implementation jargon rather than agent-facing meaning.

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 guidance, no preconditions (e.g. the component property must already exist via add_component_property), and no named alternatives such as bind_variable_to_property or set_instance_properties. The agent must infer the context entirely.

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