lattice-create

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

No annotations provided, so description carries the full burden. It doesn't disclose effects (e.g., adds a new object to the scene, affect scene state), nor does it mention return values or side effects. The description is minimal, leaving behavioral details to schema.

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?

Single sentence, front-loaded, no waste. It's concise but lacks detail; however, for a simple creation tool, this is acceptable.

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 0 required parameters, output schema absent, and low description coverage. It doesn't explain defaults (e.g., default location [0,0,0]) or how 'name' is used. For a creation tool, more context is needed: does it return a handle? Does it affect scene level? Contextual completeness is low.

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 coverage is 0%, so description must compensate, but it doesn't. It doesn't explain 'name' or 'location' beyond their titles. The schema itself is self-explanatory for these simple parameters, but description adds no value. With 0% coverage, score should be lower, but parameters are intuitive, so 3 is baseline.

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 'Create a lattice object' is clear: specific verb (Create) + resource (lattice object). It distinguishes from siblings like 'lattice-report' and 'lattice-set' but doesn't explicitly mention its relation to 'pointcloud-create' or other object creation tools. Still, it conveys the core purpose well.

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?

No guidance on when to use this tool versus alternatives like 'object-create' or other geometry creation tools. It doesn't explain when a lattice is needed or how it differs from other object types. The usage context is implied but not explicit.

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