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

With no annotations, the description carries the full burden and does so: it discloses that the lookup is live against an external system, enumerates all five status values with their exact meanings, and warns that "unverified" means nothing authenticates the correspondent's identity. This is materially more than the schema or annotations provide.

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?

Front-loaded with the core action, then the status vocabulary, then the usage rule — a sensible order. The first sentence is a long nested clause chain that takes effort to parse, which keeps it from a 5, but every clause carries information.

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?

No output schema and no annotations, yet the description covers the return shape at a useful level (account, services, renewal date, balance owed) and fully defines the status vocabulary. An agent has everything needed to call it and to interpret or abstain from the result.

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?

Only one parameter, and the schema already documents it at 100% coverage ("The id of the conversation, as list_conversations gives it"). The description adds the useful fact that the lookup is keyed by the correspondent's address rather than the id, but says nothing further about the parameter itself, so the baseline 3 applies.

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 ("reads the customer card of a helpdesk ticket") and immediately scopes it to what the account's own client area/CRM/ERP knows about the correspondent. This is clearly distinguishable from siblings like get_contact and get_conversation, which operate on stored records rather than a live external lookup.

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?

Explicitly says when to call it ("Read it before answering a customer about their account, a renewal or an invoice") and implicitly when not to act on the result, e.g. the "unverified" case warns "do not discuss their account by email". The "unavailable" case even prescribes the follow-up ("ask again later").

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