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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real value beyond them: it defines null as "not set" and explains that translate_outgoing_to, record_voice_in and send_voice_in are per-signed-in-person fields that go null with personal_settings_available=false when there is no signed-in user.

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 tight sentences with no filler: the read/scope statement comes first, followed by the two interpretation rules an agent actually needs. Every clause carries information about return semantics.

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 the description needn't enumerate returned fields, and it correctly spends its budget on the non-obvious part (per-user fields and null semantics). The remaining gap is the missing routing hint toward set_chat_language_settings for mutations.

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 coverage is 0%, so chat_id is documented nowhere, and the description only conveys indirectly that it identifies "one chat" (minLength 3 / maxLength 64 constraints are unaddressed). It does not say whether chat_id is numeric, an external key, or where to obtain it, so it only partially compensates for the coverage gap.

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 ("Read one chat's language and voice settings") plus the exact frame of reference ("as the chat language panel shows them"), and scopes it to a single chat. An agent can tell this apart from the write-side sibling without opening any 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?

Usage is only implied: the word "Read" and the readOnlyHint signal a lookup, but there is no explicit when-to-use statement and no pointer to set_chat_language_settings as the mutation counterpart. Guidance on interpreting nulls is present, but guidance on choosing this tool over its sibling is not.

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