network_manage

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

With no annotations, the description carries the burden. It lists operations and arguments, but doesn't disclose side effects, permissions, or network access implications. It does note the canonical call shape and flat parameter alias, which is behavioral detail, but lacks depth on what each scaffolding operation does to the scene or system.

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 reasonably concise and front-loads the purpose, then lists ops in a structured list. The canonical call shape note adds necessary context, though the op list could be tightened with default values shown inline.

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 has multiple ops and a simple schema, the description provides enough to call basic operations. It includes return behavior implicitly through 'list' ops and output schema existence, but could benefit from examples or error handling notes. Still, it's complete for typical use.

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%, but the description details each parameter's name, type, and default within the ops list, adding semantic meaning beyond the schema. It also clarifies the 'params' object structure and compatibility alias, which is valuable.

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 lists four specific operations under a clear 'Networking and Socket Scaffolding' purpose, each with a verb and target (e.g., 'scaffold_tcp_server'). It distinguishes from siblings by being the only tool focused on network scaffolding, though it doesn't explicitly contrast with any sibling.

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 implies usage for networking tasks by enumerating distinct ops, and the canonical call shape provides instructions on how to structure calls. However, it doesn't explicitly state when to use this tool versus siblings or when not to use it, so it misses explicit exclusion guidance.

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