net_add_replicated_component

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

With no annotations, the description carries the behavioral disclosure burden. It does disclose mutation intent, save/compile side effects, and the conditional create_if_missing behavior, which is useful. However, it does not state what happens to existing replication settings when the component already exists, whether the operation can be destructive, or what failure modes occur.

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 compact and well-structured: a one-sentence summary, an Args list, a KB pointer, and a concrete example. There is minor redundancy between component_type and create_if_missing, but no filler or wasted sentences.

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 seven parameters and no annotations, the description is reasonably complete: it covers asset scope, the conditional creation behavior, the mutation side effects, and provides a realistic example plus a KB reference. It still lacks explicit guidance on prerequisites and behavior when the target component already exists.

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 Args block is the sole source of parameter meaning. It adds genuine semantics for all seven parameters, such as 'SCS component template variable name' and the dependency between component_type and create_if_missing. The replicates description is terse but adequate for a boolean flag.

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 first sentence names a specific action ('Create or configure') and a clear resource ('a Blueprint component template for replication'), so an agent can tell what the tool does. It is clear but does not explicitly distinguish itself from the overlapping sibling net_set_component_replicates.

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 offers parameter-level guidance and an example but never states when to use this tool instead of net_set_component_replicates, net_configure_replicated_property, or other net_* tools. No explicit when-to-use or when-not-to-use guidance is present.

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