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

Annotations already declare destructive/openWorld/non-idempotent, but the description adds material context beyond them: it can charge credits and send email, it re-validates client/listing/stage and silently no-ops with an explanation, previews expire after 30 minutes, each preview is single-use, and a linked PropertyList account with CRM permissions is required. That is exactly the extra behavioral disclosure the 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?

Front-loaded with purpose and the gating rule, then the re-validation/expiry/auth caveats. Four short paragraphs with no filler, though the expiration and single-use rules could be tightened into one sentence without losing meaning.

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, credit-charging commit tool with an output schema already present, the description covers the safety gate, failure semantics, idempotency/expiry, and auth requirements. Nothing an agent needs before invoking it is missing.

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 coverage is 100% and the single action_id parameter is fully documented as 'from the preview.' The description adds only the framing that the id originates from a staged preview, which the schema already states, so the baseline 3 applies.

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 ('make a change you staged') and enumerates the exact staging siblings (move_pipeline_stage, qualify_lead, assign_listing, etc.) whose previews it commits. An agent can distinguish this from cancel_action and from the staging tools without opening any schema.

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?

Gives an explicit gating condition: 'Call it ONLY after showing the agent the preview and hearing them say yes.' That is a clear when-to-use rule, and the sibling enumeration establishes the when-not (you stage with those tools, you commit with this one).

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