network_manage

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It fails to mention side effects, permissions, rate limits, or what each operation does. This is a critical gap for a tool managing network operations.

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 short sentences with no unnecessary words. The structure is clean, but the second sentence is essential for guidance. Could be slightly more concise by integrating the reference, but overall efficient.

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 tool with 2 parameters (including a dynamic object), no output schema, and no annotations, the description is highly incomplete. It does not explain operation behaviors, required params per op, or return values. The reference to godot_catalog partially compensates but leaves significant gaps.

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% for both parameters. The description adds no additional meaning beyond the schema. Since baseline is 3 when coverage is high, this score reflects the lack of extra context for the dynamic 'params' object.

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 states it handles 'Godot network operations', which is a broad verb+resource. It does not distinguish from sibling tools like 'audio_manage' or 'scene_manage' beyond the network domain. The enum in the schema provides some specificity, but the description itself is vague.

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 advises calling 'godot_catalog for the operation tree', implying that catalog is needed for detailed operations. However, it offers no explicit guidance on when to use this tool versus siblings, no prerequisites, and no exclusion criteria.

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