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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond them by disclosing what the response contains — the ids that change_settings consumes plus per-field documentation — which is the key behavioral fact for chaining the two tools. It does not mention auth requirements or whether settings can vary by account, so it stops short of a 5.

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?

Three short sentences, front-loaded with the purpose and followed by the two actionable rules; nothing is padded. Minor wording awkwardness ('Call it without tool') and a slight restatement of the schema's omission behavior keep it from a 5.

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 carries the burden of explaining return content and does so by naming the ids and field semantics the caller receives. For a single optional enum parameter with full schema coverage, that is enough to call it correctly; only the absence of response-shape specifics (e.g. whether all groups are returned at once) leaves a small gap.

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 enum parameter is already documented in the schema, including the 'leave out to list them' behavior, which the description repeats almost verbatim. The phrase 'for one setting group' confirms scope but adds no syntax or format detail beyond the structured field, 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 ('Shows the shop's current Xyla settings for one setting group') and explicitly separates itself from the mutation sibling by describing the payload as 'the ids change_settings needs and how each field works'. An agent can distinguish it from change_settings and the other read tools without opening the 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?

Gives two concrete operating instructions: call it with no `tool` argument to enumerate the setting groups, and read a group before changing it. The second sentence is an explicit ordering rule tied to the change_settings sibling, which is exactly the when-to-use guidance that prevents blind writes.

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