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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the write/destructive profile is covered. The description adds genuine behavioral context beyond that: the edit is guarded by an optimistic-concurrency stage check and the caller must re-read state first. It stops short of saying which fields are overwritten or whether unmentioned properties are preserved.

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 with zero filler, and the core action plus the most decision-relevant constraint are front-loaded before the sibling redirect.

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, nested-parameter write with no output schema, the definition covers the stage guard and the sibling split but leaves the identity parameters and the replace-vs-merge semantics of subject/content unaddressed. Adequate to start, not sufficient to call confidently on first try.

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% and the schema includes a nested PitchEdit object, so the description must carry the load. 'At its expected stage' hints at the purpose of expected_stage as a concurrency/version guard, but campaign_id, entity_id, and the required subject/content fields inside body are never explained.

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 plus a scope qualifier ('saved, unscheduled pitch'), which immediately separates it from edit_upcoming_send and from draft-generation siblings like generate_pitch_drafts/rewrite_pitch_drafts. An agent can route correctly without opening the 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 pre-condition ('Refresh before editing') and an explicit exclusion with the alternative named ('scheduled messages use edit_upcoming_send'). This is when/when-not/alternative guidance in one compact sentence.

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