net_configure_replicated_property

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

With no annotations, the description must carry the full burden of behavioral disclosure. It lists supported replication_condition values, which is useful, but it does not mention side effects, whether the operation is reversible, if it triggers compilation/saving (though the save/compile parameters hint at that), or any failure conditions. The description also does not explain how replication_mode and replication_condition interact or what happens to existing settings. This is insufficient for a mutation tool.

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, with the core purpose stated upfront followed by supported values and an example. It is structured logically and not overly verbose. The list of values is necessary, though it could be compressed. The KB link and example are useful additions. Overall, it is well-organized and front-loaded.

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 six parameters, two required, and no schema descriptions or annotations, the description is incomplete. It does not explain the optional parameters, prerequisites, error scenarios, or return values (though an output schema exists, it is not shown). The description lacks context about when to use replication_mode versus replication_condition, and does not mention any setup requirements. This leaves significant gaps for an agent to safely and correctly invoke the tool.

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 only partially explains replication_condition by listing valid values, but it does not explain the meaning of replication_mode, save, compile, or the required blueprint_name and variable_name beyond the example. The description adds limited value for replication_condition but leaves the other five parameters undocumented, which is inadequate for a tool with six parameters.

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 tool's purpose: to configure an existing Blueprint member variable's replication mode (none, replicated, RepNotify). It identifies the specific resource (Blueprint member variable) and the action (configure), which is unambiguous. However, it does not differentiate from closely related siblings like net_set_property_replicated or net_set_replication_condition, so it lacks explicit sibling distinction.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, conditions, or exclusions. The example and KB link are helpful but do not clarify when this tool should be chosen over other net_* tools. There is no 'when to use' or 'when not to use' context, leaving the agent to infer usage.

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