net_set_component_replicates

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

With no annotations, the description must carry the full burden of explaining side effects, but it only says 'configure replication-by-default' without disclosing whether this modifies the asset persistently, requires compilation, overwrites existing settings, or affects currently placed instances. The example shows required parameters but does not explain the behavioral implications of the save and compile flags.

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 appropriately short, leads with the core purpose, and includes a concrete example plus a KB reference. It is efficient and easy to parse, though the KB link is not self-contained.

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 five parameters, zero parameter descriptions, no annotations, and a supervisory KB reference, the description is incomplete for an agent that needs to invoke this tool correctly. It omits the meaning of the boolean flags and fails to explain what 'replication-by-default' concretely changes in the component template.

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, but it only illustrates blueprint_name and component_name usage. The optional parameters save, compile, and replicates are entirely unexplained, leaving their semantics to the schema's bare titles and defaults.

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 uses a specific verb and resource: 'Configure replication-by-default on a Blueprint SCS component template.' This clearly identifies the tool's action and target, and the example reinforces the intended use. It does not explicitly contrast with sibling tools like net_set_actor_replicates, but the 'component template' phrasing offers reasonable differentiation.

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 given for when to use this tool versus alternatives such as net_set_actor_replicates, net_configure_replicated_property, or net_set_property_replicated. The KB link is too vague to serve as actionable routing guidance, and there are no stated prerequisites or exclusions.

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