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

Annotations already declare destructiveHint=true, openWorldHint=true, and readOnlyHint=false, so the mutation risk is covered structurally. The description adds one genuinely useful piece of context — that the change affects every environment — but says nothing about what settings get overwritten, permission requirements, or how the optimistic-concurrency 'expected version' check behaves on conflict.

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 short, front-loaded sentences with no filler. It is efficient, though the first sentence duplicates the title verbatim, which slightly reduces the value of the space used.

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 seven-parameter, six-required destructive mutation with no output schema and 43% schema coverage, the description is far too thin. It omits the meaning of most required fields, the consequence of the version mismatch, and any recovery/idempotency guidance despite an idempotency_key parameter being present.

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 only 43%, so the description must compensate, and it does not. It nods at 'expected version' (matching the already-documented expected_version) but leaves name, note, company, timezone, and workflow wholly unexplained, including no clarification that six of seven params are 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+resource ('Update company-wide settings'), which is clearly distinguishable from the sibling summer_company_settings_read. However, the sentence essentially restates the title and never explicitly names the read counterpart as the alternative.

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?

No guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The only contextual remark ('Affects every environment') is a blast-radius warning rather than usage routing.

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