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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description still adds genuinely new behavioral context — that AI credit status is included and that no credits causes the visitor-facing bubble to be hidden — which explains a state an agent would otherwise misread as a configuration bug. It stops short of covering behavior when chat is unconfigured.

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?

A single front-loaded sentence with no filler; the field enumeration reads as a compact manifest of the return payload, which is doing real work rather than padding. Every clause maps to something the caller gets back.

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?

There is no output schema, so the description shoulders the burden of describing the return payload, and it does so item by item while also flagging the credits/bubble dependency. It does not cover the empty or unconfigured case, which is the main remaining gap for a getter.

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 exists and the schema documents it fully ('Site id.'), so the 100% coverage baseline of 3 applies. The description refers to 'the site's' settings but adds no detail on how a site is identified or what happens when id is omitted (it is not required).

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 resource (site chat bot settings), then enumerates exactly which settings are returned: on/off, assistant name, greeting, owner instructions, lead capture fields, lead destination, and AI credit status. That enumeration makes it unmistakable against the sibling mutator set_site_chat and against unrelated getters like get_site_email.

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 read-vs-write distinction from set_site_chat is implied by the verb 'Read' and the tool name pairing, but the description never says when to call this versus set_site_chat or other site getters, nor does it state prerequisites such as a required site id or selection state. Usage is inferable rather than stated.

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