Add Rule To Topology

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so safety is covered. The description adds only that a destination feature class can be specified; it says nothing about required preconditions (existing topology, participating feature classes) or what constitutes a valid rule_type, leaving the mutation's behavior largely opaque.

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?

A single, compact sentence with no filler, front-loading the core action. It is efficient, though arguably under-specified rather than optimally concise.

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?

An output schema exists so return values need not be explained, but the mutation logic, prerequisites, and the four undocumented parameters are not addressed. For a topology-editing tool with 0% schema coverage, this leaves the agent without enough to construct a correct call.

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 carry the parameter burden. It gestures at rule_type ('precision rule') and destination_feature_class, but provides no meaning for topology_path, origin_feature_class, or valid rule type values, and does not explain the origin/destination pairing semantics.

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 names a specific verb (add) and resource (rule to topology), and clarifies that a destination feature class may be specified, which distinguishes it from the sibling remove_rule_from_topology. However, it does not explicitly contrast itself with the other topology siblings such as add_feature_class_to_topology or create_topology.

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?

There is no statement of when to use this tool versus alternatives, nor any prerequisites. An agent gets no indication that a topology must already exist or that the feature classes must already be included before a rule can be added.

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