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

Annotations already declare destructiveHint=true and idempotentHint=false, so the description needed to explain *what* is destroyed or replaced. It does not say whether specifying only `body` wipes `subject`, whether the edit resets the pitch's state or invalidates a prior quote, or whether ownership/permission constraints apply. "Owner's edits" and "draft" add a little framing, but net disclosure beyond the annotations is thin.

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?

A single front-loaded sentence with no filler, which is structurally fine, but the brevity here is under-specification rather than economy — there is nothing to be concise about because almost no information is conveyed.

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, non-idempotent mutation with three parameters (one undocumented), no output schema, and a whole sibling cluster of pitch operations, the description is far too thin to let an agent call it confidently. Missing: partial-vs-full replacement semantics, allowed pitch states, and the relationship to the quote/approve/reject flow.

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 33% — `pitchId` and `subject` carry no descriptions, and `subject`'s 140-char limit and optionality go unexplained. The description adds no parameter meaning whatsoever, so it fails to compensate for the coverage gap.

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?

The sentence gives a verb and a resource ("Save the owner's edits to a pitch draft"), so the basic operation is inferable. But it doesn't distinguish itself from close siblings like soclo_creators_pitch, soclo_creators_pitch_approve, soclo_creators_pitch_reject, soclo_creators_pitch_replied, or soclo_creators_pitch_sent, and the drift between title ("Edit a pitch") and description ("pitch draft") leaves the target object mildly ambiguous.

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?

There is no when-to-use guidance at all: nothing says whether this requires a prior quoting step (cf. soclo_creators_pitch_quote, soclo_creators_prices), whether an approved or already-sent pitch can still be edited, or how this differs from approve/reject. The agent must guess the workflow position of the tool.

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