lattice.create

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

Without annotations, the description carries the full burden. It solely states 'Create a lattice object' without disclosing behavioral traits such as whether it requires a specific 3D view mode, if it creates a new object in the scene, or if it overwrites an existing lattice. No side effects or dependencies are mentioned.

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 extremely concise (3 words), but it is under-specification rather than effective conciseness. It is not front-loaded with key details, and each word does not earn its place because critical context is missing. A better description would add behavioral or parametric context without being verbose.

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 tool's simplicity (2 optional params, no output schema), the description is incomplete. It does not convey what happens after creation, how the location parameter affects the lattice, or whether an object is immediately visible. Complete documentation would at least hint at the outcome or side effects.

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 input schema has 2 parameters with 0% description coverage. The description does not add any meaning beyond the schema's field names and types. It fails to explain the purpose or effect of 'name' and 'location', which is especially needed since they are optional and have no enums.

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' provides a specific verb and resource, clearly distinguishing it from sibling tools like lattice.report and lattice.set. It is unambiguous and directly states the tool's function.

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 offers no guidance on when to use this tool versus alternatives. It does not mention prerequisites, contexts (e.g., required mode), or when not to use it. Given the presence of many related tools (e.g., object.create, mesh.create), this is a significant gap.

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