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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new semantics: that the return is a list of attribute keys and that an empty list means no attributes are required — information an agent cannot get from annotations or the schema.

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 with no filler: the first defines what is read and how to interpret the result, the second gives the call timing. Nothing is wasted and the key semantic (empty list = none) is front-loaded.

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?

With no output schema, the description usefully explains the return shape and the empty-list edge case. It leaves minor ambiguity about scope (account-wide vs. per-inbox) but covers everything needed to invoke the tool 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 100% and the single optional 'fields' parameter is documented in the schema as a projection filter. The description adds nothing about it, but with only one fully documented parameter the baseline of 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 ('Read') and a precisely scoped resource ('attribute_keys of the conversation custom attributes that must be filled before a conversation can be resolved'). This is clearly distinct from the sibling update_conversation_required_attributes, though the write counterpart is alluded to rather than named.

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 closing instruction 'Call before making a change' gives an explicit trigger for invocation and implicitly frames this as the read step preceding the update tool. It stops short of naming the alternative tool or stating any when-not-to-use condition, so it falls just short of a 5.

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