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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds genuinely new behavioral information: editing an approved email resets its approval state, a side effect not derivable from the annotations. It still doesn't say whether only the supplied fields change or the whole draft is replaced.

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, both front-loaded and free of filler. 'With the owner's words' is slightly ambiguous phrasing but the sentence still earns its place by hinting at authorship/voice.

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 three-parameter mutation with no output schema, the definition covers the approval-reset side effect but leaves messageId undefined and doesn't clarify partial-update semantics. Annotations handle the destructive/read-only profile, so nothing critical about safety is missing, but the input contract is under-explained.

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%, so the description must carry parameter meaning, and it only loosely maps 'subject' and 'text' to two of the three fields. The required messageId — the key identifying input — is never mentioned, and there is no indication that subject/body are both optional with length limits.

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: change a draft's subject or text. An agent can tell this is an in-place edit of an existing draft message, not a creation or approval. It doesn't differentiate itself from nearby siblings such as soclo_leads_draft or soclo_posts_edit_draft, so it stops short of a 5.

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?

Usage is only implied: 'a draft' and 'an approved email' signal this operates on an existing draft, likely one already approved or awaiting approval. There is no explicit statement of when to use this versus soclo_leads_draft (create), soclo_leads_approve, or soclo_leads_reject, and no prerequisites are given.

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