Bind Variable

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

The description adds context beyond the annotations by explaining that null values in bindVariables unbind a variable and giving ordering constraints. It does not contradict the openWorldHint and idempotentHint annotations. Slightly lacking in detail about error handling or side effects.

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?

Three focused sentences: purpose, when-to-use, prerequisites. No filler. Front-loaded with the primary action.

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?

With an output schema present, the description focuses on input and usage, which is appropriate. It covers when to use and ordering constraints. Could be more complete by explaining what happens on invalid variable IDs, but overall adequate given sibling tools and rich schema.

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 already describes all parameters with 100% coverage. The description adds value by explaining the usage pattern (e.g., 'E.g., { 'fills': 'VariableID:1:2' }') and the dual role of setting modes, which goes beyond the schema's property definitions.

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 binds a variable to a node property or sets explicit variable modes, and distinguishes it from literal node_set_* tools by noting when to use this instead (when tracking a design token).

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 explicit ordering rules (set auto-layout before binding padding/spacing; set solid fill before binding colour token) and a clear alternative (use instead of node_set_* when tracking a design token). This helps the agent decide when to invoke this tool.

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