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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description adds important context beyond that: mutation is gated behind human approval in Settings > MCP plus an execute_approved_action call, and admin-configured approval policy may vary. That materially changes how an agent should plan the call. It still does not say what is overwritten when only part of the data object is supplied.

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?

Four sentences, no repetition, and the core action and approval gate come early. The first sentence about RetailHardHat field_operations is boilerplate that does not earn its place, but overall it is tight.

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 and annotations cover the safety profile, so return values and risk are handled elsewhere. The gap is parameter semantics for a 2-parameter tool with a large nested payload and 0% schema coverage; the description should at least note that data fields are optional/partial-update or full-replacement to let the agent construct the call correctly.

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%, and the nested data object has roughly a dozen fields (status enum, utilityType enum, dates, UUID references, estimatedLeadTimeDays) with no descriptions in either the schema or the description. The description contributes nothing about utilityConnectionId or field-level meaning, leaving the agent to infer everything from property names.

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: 'Edit a utility connection.' That is enough to distinguish it from create_utility_connection, delete_utility_connection, and list_utility_connections. The opening 'Use this when working with RetailHardHat field_operations records' is generic boilerplate rather than a differentiating statement.

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?

It provides a real usage condition: no change occurs until a human approves the request and execute_approved_action is called. However, it gives no guidance on when to choose this over siblings like update_utility_company or when an edit should instead be a create/delete, and the 'business workflow approvals always apply' line is vague.

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