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

Annotations only declare mutation/idempotency/open-world traits; the description adds real behavioral context: who is affected ('Existing room viewers may see the additions'), what is preserved ('Older pinned items and existing access controls remain unchanged'), and what side effects are absent. That is the kind of disclosure annotations cannot carry.

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?

Four tight sentences, front-loaded with the confirmation requirement and version preconditions before the side-effect caveats. No filler or restated title text.

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?

With an output schema present, return values need no explanation, and the description covers confirmation, versioning, access prerequisites, and additive side effects. The remaining gap is the unmentioned project_id/idempotency_key semantics, which the 0%-coverage schema leaves undocumented.

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% across 4 parameters, so the description must carry the load. It hints at expected_version/room_fingerprint ('current close and room versions') and constrains report_ids to approved/published revisions, but says nothing about project_id, idempotency_key, or confirmation_token.

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 ('add exact approved and published report revisions to a reviewed SparkRoom') with qualifiers that narrow scope beyond the generic sibling sparkroom.add_documents. An agent can tell this is a versioned, review-gated room refresh rather than a general document insert.

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?

States the preconditions clearly ('After confirmation', 'Requires current close and room versions plus Growth access') and carves out what it is not for ('does not send an invitation or create a share link'). It never names a sibling alternative by name, so it stops short of a 5.

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