add_network

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

No annotations are provided, so the description carries full burden. It reveals the tool creates a logical network (a write operation) and gives platform-specific behavior. However, it lacks details on failure modes, permissions, or side effects. The behavioral context is adequate but not exhaustive.

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?

Two concise sentences: first defines purpose and scope, second gives exclusion and alternative. No wasted words, front-loaded with key information.

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 no annotations and no output schema, the description is fairly complete. It explains the tool's function, when to use it, and provides a parameter example. It lacks details on return values or error handling, but for a create tool this is acceptable.

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 description coverage is 0%, so the description must compensate. It provides an example for 'family' ('Ethernet'), adding meaning beyond the schema. However, it offers no additional explanation for 'name'. The compensation is partial but not complete.

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 action ('Create') and resource ('logical network'), specifies target platforms (Premium/Quantum), and gives an example for the 'family' parameter ('Ethernet'). It also differentiates from sibling tools by explicitly stating when not to use it (M340/M580).

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?

Explicitly states when to use (Premium/Quantum platforms) and when not to (M340/M580), with an alternative action ('configure communication on modules/DTMs instead'). This provides clear guidance and distinguishes from siblings.

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