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

Annotations declare readOnlyHint=false with destructiveHint=false, leaving the side-effect profile ambiguous, and the description resolves it usefully: the draft is generated but not published, the user posts it. That is real context beyond the annotations. It still omits what happens on regeneration or how the idempotency key affects repeat calls.

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 tight sentences with the purpose front-loaded and the side-effect caveat immediately after. No filler; every clause carries information.

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?

The non-publishing behavior is covered, which is the most important unknown for a generation tool with no output schema. But with 6 parameters at 0% coverage and no output schema, an agent still lacks guidance on idempotencyKey, regenerate, and the required identifiers, so the definition is only marginally sufficient.

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 six parameters, so the description carries the full burden, yet it only alludes to 'the chosen tone' and never explains the peer/expert/founder enum, regenerating, siteId, mentionId, projectId, or the required idempotencyKey. Most parameters are undocumented in both places.

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 (draft) and a specific resource (a reply to a lead's post), which is enough to tell it apart from generic generation tools. However, it does not differentiate itself from the sibling update_lead_reply, which an agent could easily confuse with this one.

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?

The description says nothing about when to use this tool versus update_lead_reply, prepare_outreach_draft, or create_outreach_draft. The clause 'Nothing is posted' clarifies workflow outcome but is not usage guidance or an exclusion, so an agent gets no routing help.

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