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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds substantial non-obvious behavior: the change is staged and inert until a human approves and execute_approved_action is invoked, and org-level vs. business-workflow approval rules differ. It does not clarify whether the nested data object is a partial patch or a full replace, which matters for a destructive update.

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 approval workflow content is front-loaded and earns its place, but the opening sentence ("Use this when working with RetailHardHat field_operations records in the connected organization") is boilerplate that could be dropped or merged. The remaining sentences are tight and non-redundant.

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 no explanation. The gaps are on the input side: partial-update vs. replace semantics for the data object and which nested fields are mandatory are left entirely to inference, which is thin for a destructive, non-idempotent mutation.

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 only parameter documentation is the schema's types and the utilityType enum; the description says nothing about utilityCompanyId or any of the eight nested fields. With a nested object where it is unclear which subfields are required versus optional, the description should compensate and does not.

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?

"Edit a utility provider" gives a specific verb and resource, and the tool name plus sibling set (create_utility_company, delete_utility_company, update_utility_connection) make the target obvious. The description does not explicitly contrast itself with those siblings, and the opening clause about RetailHardHat field_operations records is generic framing rather than purpose.

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 approval-flow sentences explain the procedural path (human approval in Settings > MCP, then execute_approved_action), which is genuinely useful for deciding how to act. However, there is no guidance on when to choose update vs. create/delete or update_utility_connection, and no prerequisites such as required IDs or permissions.

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