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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that MCP approval requirements are org-configurable and business workflow approvals still apply, which is useful but generic boilerplate. Nothing is said about behavior for a missing/invalid ID or the approved-action flow.

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?

Three short sentences with front-loaded purpose, which is good, but the middle approval sentence is boilerplate that repeats across the tool set and occupies a third of the text without adding tool-specific value.

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 a single-parameter read is a simple surface. Still, the description gives no hint about identifier sourcing (e.g., obtain from list_utility_connections) or behavior on not-found, which would matter for an agent chaining calls.

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%: utilityConnectionId has only a uuid format and pattern, with no prose explaining whether it is the connection ID versus the utility company ID. The description does not compensate at all, so an agent must infer the identifier's meaning from the name alone.

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 sentence 'Read a utility connection' names a specific verb and resource, and the surrounding siblings (list_utility_connections, update_utility_connection, delete_utility_connection) make the single-record read scope clear. It does not explicitly contrast with list_utility_connections, but the singular/read framing is unambiguous enough for an agent.

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?

'Use this when working with RetailHardHat field_operations records in the connected organization' is a domain preamble, not a condition that selects this tool over list_utility_connections or get_utility_company. The only other sentence covers approval requirements, which is an execution constraint rather than a when-to-use rule.

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