Connection Repair Apply

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

Annotations already disclose non-read-only, idempotent, non-destructive behavior, so the bar is lower; the description still adds real value by explaining the token-validation guard and the staleness/tamper rejection semantics. A useful behavioral disclosure not present in annotations, though it omits what happens to already-repaired connections.

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 dense sentence that front-loads the action and then the guard condition. No filler; every clause contributes, though the grammar is packed and could be split for 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?

An output schema exists, so return values need not be described, and the safety annotations cover part of the behavior. However, for a mutation tool with 0% schema coverage, the description leaves the required preflight workflow and the aprx_path parameter ambiguous for an agent.

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 load. It clarifies that repair_token is a preflight token and that repairs constitutes a 'repair plan', which maps two of three params, but aprx_path and the internal shape of the repairs array remain unexplained.

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?

States a specific verb and resource: applying bulk data source repairs to a project. The precondition clause ('only when the repair plan and target connections are unchanged') further narrows scope, and the pairing with arcgis_pro_connection_repair_preflight is inferable. It does not explicitly name the preflight sibling, so it falls just short of full sibling 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?

The description implies a preflight token must exist and be fresh, which hints that a preflight step must precede this call, but it never states 'run arcgis_pro_connection_repair_preflight first' or contrasts with alternatives like arcgis_pro_repair_layer_source. Usage is implied rather than prescribed.

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