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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description still earns credit by explicitly reinforcing that nothing is verified or changed and by naming the exact data surfaced, which goes beyond the annotation set. It omits auth/permission prerequisites, but for a zero-parameter read this is a minor gap.

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?

Two short sentences, front-loaded with the positive scope and closed with the negative scope. Every clause carries information and there is no filler or restatement of the title.

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-value documentation is not the description's burden, and the annotations carry the safety and idempotency profile. What remains — what is read and what is deliberately not done — is fully stated, making the definition complete for this simple, parameterless read tool.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate. Per the baseline for zero-parameter tools, a 4 is appropriate; the description correctly avoids inventing arguments and instead spends its words on scope.

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 opens with a specific verb+resource ("Read the name, email and phone on the customer's Jerry account") and enumerates the exact fields returned, including phone verification status. The resource "account" is distinct from the sibling tools that deal with quotes, status, and applications, so an agent can route correctly without opening a schema.

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 doesn't verify an email or change any insurance information" gives a clear negative-scope signal that steers the agent away from mutation flows. However, it never names an alternative tool (e.g. jerry_update_application) or states the condition under which this read tool should be preferred, so it stops short of full when/when-not/alternatives guidance.

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