define_grid

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

With no annotations, the description must disclose behavioral traits. It states 'store or overwrite', implying mutation, and mentions units (mm). It does not clarify idempotency, destructive effects on existing grids, or concurrency behavior. Adequate but not thorough.

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 short (4 sentences), front-loads the purpose, and uses bullet-like formatting for x_lines and y_lines. 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?

The tool has 5 parameters and an output schema. The description explains the two most important parameters and suggests verification. Missing explanation for z_base_mm and description, but overall it's fairly complete for the complexity level.

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 description adds meaning to the key parameters x_lines and y_lines by explaining their orientation ('vertical, parallel to Y axis' and 'horizontal, parallel to X axis'), which is absent from the input schema (0% coverage). It does not explain z_base_mm or description, but the core parameters are clarified.

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 verb 'Store or overwrite' and the resource 'named grid definition'. It differentiates from sibling tools like 'delete_grid' and 'list_grids' by specifying the action of defining grid lines.

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 advises to 'Call get_grid_lines to verify after defining', which provides post-use guidance. However, it does not explicitly state when to use this tool versus alternatives like 'delete_grid' or 'list_grids'.

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