lattice_delete_network

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

Description labels the tool as 'Destructive' but lacks further details on consequences, reversibility, or side effects. With no annotations, more behavioral context is needed.

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?

Extremely concise (two short sentences). Front-loaded with action and resource. However, under-specification limits usefulness.

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?

For a simple deletion tool, the description lacks detail on return values, prerequisites (e.g., network must exist), and idempotency. Incomplete for confident usage without external knowledge.

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 100%, with one required id parameter described as 'Network ID'. Description adds 'by its Lattice ID' but this does not add meaningful semantics beyond the schema.

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?

Description clearly states the tool deletes a tracked network by Lattice ID, using specific verb and resource. However, it does not differentiate from sibling tools like lattice_delete_worker_network, which also delete networks.

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 (e.g., lattice_delete_worker_network). No explicit when or when-not criteria provided.

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