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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, so the safety profile is carried by structured data. The description does add real value beyond that — it scopes the blast radius ("retains the original analysis and source references; does not change cases or company knowledge") and the expected_revision wording signals an optimistic-concurrency check. It does not say what happens on a stale revision (error vs. overwrite) or whether a prior disposition is replaced.

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 sentences, verb-and-resource front-loaded, with the effect-scope caveat second. No filler or restated field names.

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 destructive, open-world mutation with 7 required parameters and near-zero schema descriptions, the definition covers intent and effect scope but leaves the caller guessing on parameter meaning, revision-conflict behavior, and required permissions. No output schema exists, so some of that burden falls here.

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 13% across 8 parameters — only idempotency_key is documented in the schema. The description restates that a theme and disposition exist and that a revision is expected, but never explains what the integer `theme` references (index vs. id), what `report`/`company` identify, or how the three disposition enum values differ semantically.

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?

Names a specific verb and resource: "Record a human disposition on a saved recurring-issue theme at its expected revision." That distinguishes it from the read-only siblings (summer_reports_themes_get / _list) and the generative one (summer_reports_themes_generate). It stops short of naming those siblings explicitly.

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 phrase "a human disposition" implies this is the human adjudication step after theme generation, but no when-to-use, prerequisites, or exclusion against the sibling tools is stated. The requirement to supply an expected revision is implied but never framed as a precondition an agent must satisfy first.

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