modify_dimension

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

No annotations are provided, so the description carries the full burden. It indicates the tool modifies a dimension and returns updated state, but does not disclose error handling, side effects, or requirements (e.g., feature must exist). Some unit context is given but behavioral details are lacking.

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 concise, front-loads the purpose, and uses a clear argument list. It is slightly verbose with examples but overall efficient and well-structured.

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 the complexity (3 required params, no output schema, no annotations), the description covers basics but lacks depth. It does not explain what happens if the dimension is invalid, locked, or suppressed. Adequate but leaves gaps.

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?

With 0% schema description coverage, the description explains all three parameters with examples and unit guidance (mm for linear, degrees for angles). It adds significant value beyond the schema's bare titles, though ranges or exact format are absent.

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's purpose: 'Change a single dimension on a feature.' It specifies the resource (dimension) and the action (change), and distinguishes from sibling tools as the only one modifying existing dimensions.

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?

The description implies usage in active part or assembly with examples, but does not explicitly state when to use this tool versus alternatives, nor provides exclusions or prerequisites. Guidance is minimal.

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