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

Annotations already flag destructiveHint=true and openWorldHint=true; the description adds real value on top by bounding the blast radius ('other participants' versions are never touched'), naming the write scope required ('Requires recordings:write scope'), and disclosing what inputs drive the regeneration (current workspace prompt, per-call prompt, notes, note template). A small gap: it never says outright that the caller's existing summary is replaced/overwritten by the new one.

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?

Front-loaded with the core action and scope, and each clause carries information (scope, inputs, cost comparison, return value, auth). Dense parenthetical enumerations ('workspace prompt, per-call prompt, notes and note template') make it slightly heavy, but nothing is filler.

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 4-parameter mutation with no output schema, the description covers the essentials: it states the return value ('the new summary text'), the required scope, and the isolation guarantee. It does not address whether regeneration is synchronous/long-running or what happens on failure, which would matter for a reprocessing call.

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%, so account/workspace/saveToDb/recordingId are all documented structurally; baseline 3 applies. The description adds behavioral rather than parameter-level meaning — it explains which instruction sources feed the run, but says nothing about saveToDb preview behavior or workspace selection that the schema doesn't already cover.

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?

Specific verb ('Re-run the analysis') and precisely scoped resource ('the CALLER's own version of the summary, key points, action items, enhanced notes'), with the negative scope stated explicitly ('Other participants' versions are never touched'). It is also unambiguously distinguished from the closest sibling, hub_reprocess_recording.

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?

Explicitly positions itself against the alternative by stating it is 'Cheaper than hub_reprocess_recording', and clarifies the scope condition (caller's own version only, enhanced notes only when notes exist). It stops short of stating the inverse condition — when an agent should choose hub_reprocess_recording instead (e.g., to touch other participants' versions).

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