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

Beyond the readOnlyHint/non-destructive annotations, it discloses the precise write semantics: loading shows values but saves nothing, and only the human Freigeben click performs the write. It also warns against exposing hidden approval metadata and against inferring approval from chat text, and states that absence of host UI means no write at all.

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?

Purpose and the no-save-on-load guarantee are front-loaded, and every sentence carries a distinct constraint. The telegraphic clauses ('No save on load. Only its Freigeben click writes.') are efficient but slightly clipped, costing a little readability.

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?

For a UI-card renderer with no output schema, the description covers the essential behavior an agent needs: trigger, inputs, the fact that no write occurs on load, and the human-only write path. It does not address behavior on a stale or mismatched revision, which is a minor omission given the emphasis on using the 'exact read revision'.

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 0%, so the description must carry the load. It usefully implies that expectedRevision must be the exact revision obtained from the preceding read (optimistic concurrency) and that 'change' corresponds to the setting patch, but it says nothing about the business vs. brand variants or their fields, leaving the oneOf structure to the schema.

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 gives a concrete verb and outcome: it shows normalized before/after values for a business settings change in a human Owner card, which is distinguishable from confirm_business_settings and the other show_* approval siblings. The framing is slightly idiosyncratic ('human Owner card'), but the resource and the effect are unambiguous.

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?

It names the trigger condition ('After an explicit business settings change request'), the required inputs ('exact read revision and change'), the forbidden alternative ('Never call confirm_business_settings from the model'), and a fallback ('No host UI means no write; use the existing settings page'). When-to-use, when-not-to-use, and the substitute path are all explicit.

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