ue_net_info

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

With no annotations, the description fails to explicitly state that this is a read-only query or discuss any side effects, error conditions, or requirements. It only lists the contents of the output, which is useful context but not full behavioral disclosure.

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 a single concise sentence with a clear list; no redundant words. It is front-loaded with the main subject.

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 output schema and no annotations, the description lacks guidance on the return format, parameter usage, and any prerequisites. It provides a useful overview of the data content but is insufficient for correct invocation.

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%, and the description never explains the required 'blueprint_path' parameter. It mentions 'a Blueprint' but does not clarify whether the path should be a file path or asset name, leaving the agent without needed semantics.

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 indicates the tool retrieves a Blueprint's network state, listing specific attributes (replication, dormancy, frequencies, priorities, relevancy, and which components replicate). It distinguishes from sibling setter tools like ue_set_replication, though it lacks an explicit verb like 'get' or 'list'.

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 is provided on when to use this tool instead of siblings; it does not mention alternatives or prerequisites such as having a loaded Blueprint. Usage is only implied by the word 'info' in the name.

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