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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely useful context beyond that: API-key scoping ('you is the teammate who made this key. A key made by an agent lists only that agent') and the fact that the result is app-wide and identical across platforms. It stops short of noting permissions required or any edge cases for a missing setting, but the added disclosure is substantial.

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?

The key answer (who customers see, and the 'team'/'person' modes) is front-loaded, and the dense field-by-field sentences about teammates/profile/custom/shown earn their place because no output schema exists. Phrasing like 'as the dashboard's chat design and Profile show it' is slightly clunky, but there is no filler to cut.

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 carries the burden of explaining return values, and it does so thoroughly: signing, photos, names, teammates, per-teammate sources, and the 'you' field. Given a one-parameter read-only tool, this is close to complete; only explicit usage guidance and error behavior (e.g., when 'custom' is null or no setting exists) are missing.

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 100% and the single optional appId is fully documented in the schema, so the baseline applies. The description reinforces the app scoping ('The setting belongs to the app') but adds no format or fallback detail for appId beyond what the schema already says.

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 identifies a specific resource — who customers see on replies in an app's support chat — and the two modes ('team' vs 'person'), which is enough to distinguish it from siblings like get_setup or get_account. However, there is no explicit verb ('returns'/'retrieves'); it reads as a description of the data rather than an action, so it falls just short of a crisp verb+resource statement.

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?

There is no statement of when to call this versus alternatives, no mention of prerequisites, and no exclusion conditions. The closest thing is the note that the setting is app-scoped, which is behavioral context, not usage guidance. An agent must infer its purpose from the field documentation alone.

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