net_add_repnotify_variable

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the operation ('Add... configure') but does not explain side effects: whether an existing variable is overwritten, whether save/compile parameters trigger blueprint recompilation, what RepNotify actually does at runtime, or whether the mutation is reversible. For a blueprint-mutating tool this is a meaningful gap.

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 front-loaded with the core action. The supported-types list and the example each earn their place, and the KB pointer is a relevant reference. No filler or repetition of schema defaults.

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 7 parameters, no annotations, and zero schema descriptions, the description is under-equipped: it clarifies variable_type but leaves replication_condition, default_value, save, and compile semantically unexplained, and discloses no behavioral consequences. The output schema covers return values, which helps slightly, but an agent cannot confidently invoke this tool correctly for non-default cases.

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?

With 0% schema description coverage, the description must compensate, and it partially does: it enumerates all valid variable_type values and shows a concrete example for blueprint_name and variable_name. However, it fails to explain replication_condition options (central to a RepNotify tool), the expected format of default_value for non-string types, or the meaning of save and compile. The compensation is real but incomplete.

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 states a specific verb+resource: 'Add a Blueprint member variable and configure it for RepNotify.' This clearly identifies the operation and its unique combined scope, which implicitly differentiates it from siblings like add_blueprint_variable (add only) and net_set_replication_condition (configure only). It stops short of explicitly naming those alternatives, so it is clear but not fully differentiating.

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 explicit when-to-use or when-not-to-use guidance is given. The example call and KB pointer imply usage context, but the description never tells the agent when to choose this tool over add_blueprint_variable or net_configure_replicated_property, and there is no mention of prerequisites such as whether the blueprint must already exist or be open.

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