cad_set_variable

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

Discloses update-or-create behavior and expression format with examples, which goes beyond basic description. No annotations provided, so description carries full burden; it covers key behavioral traits.

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?

Two sentences, front-loaded with main action, no superfluous words. Every sentence adds value.

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 core behavior and parameter use for expression, but missing parameter descriptions for IDs and name. Adequate for a tool with no output schema or annotations, but not fully 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?

Only the 'expression' parameter is partially described with an example. Other required parameters (documentId, workspaceId, elementId, name) are not explained, and schema coverage is 0%.

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?

Clearly states 'Set a part-studio variable' and distinguishes from sibling tools like cad_get_variables. Provides specific action and resource, with update-or-create behavior.

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?

Implied usage for setting variables, but no explicit when-to-use or when-not-to-use compared to alternatives. No prerequisites or exclusions mentioned.

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