net_set_replication_condition

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

There are no annotations, so the description carries the behavioral burden. It does disclose that the variable must already exist, that save/compile happen after mutation, and it points to KB documentation. Still, it does not explain runtime replication effects, error conditions, or what happens to already-spawned actors, so transparency is adequate but incomplete.

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 compact and well-structured with a one-line purpose, an Args block, a KB pointer, and an example. It front-loads the key action before parameter details. Minor redundancy in the save/compile lines does not significantly hurt readability.

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?

The tool has 6 parameters, no annotations, and touches nuanced networking/Blueprint concepts. The description covers parameter meaning and gives an example plus KB reference, but it lacks guidance on expected asset path formats, validation behavior, or post-mutation effects beyond saving and compiling. The presence of an output schema reduces the need for return-value documentation.

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%, but the description compensates by explaining each parameter: blueprint_name is 'Actor Blueprint asset name or path,' variable_name is an existing member variable, and replication_condition lists representative values. It also gives allowed values for replication_mode and a concrete example, which is useful beyond the bare schema.

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 opens with a specific verb and resource: 'Set the lifetime replication condition for a Blueprint variable.' It is clear about what the tool does. However, it does not explicitly distinguish itself from closely related siblings like net_set_property_replicated or net_configure_replicated_property, so it misses the top score.

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 when-to-use or when-not-to-use guidance and names no alternatives. Given the dense sibling list of networking tools, an agent is left to infer when this tool should be chosen over net_set_actor_replicates, net_add_repnotify_variable, or net_configure_replicated_property.

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