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

Annotations only cover the safety profile (write, non-idempotent, non-destructive, open-world). The description adds genuinely new behavioral facts: the output is a reviewable draft, not a scheduled post, it returns a voice-match score, and it consumes the monthly PersonaForge post allowance — the quota disclosure is especially valuable for a metered write.

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 core action (write a post in a persona's voice) front-loaded and the caveats (review-only, quota) trailing. No filler or redundancy.

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?

With no output schema, the description usefully mentions the voice-match score return and the review-queue behavior. For a three-parameter write tool it covers the essentials, though it could note whether the persona must exist or how the result is later located (e.g., list_drafts).

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 100%, so all three parameters are already documented, including the persona_id 'omit to use own voice' behavior that the description repeats. The description adds no format, range, or validation detail beyond the schema, 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 — write a post in a persona's voice — and clarifies the persona-less fallback (the user's own trained voice). It is easy to separate from generate_persona_reply and generate_posts, though it never names those siblings explicitly.

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 post is saved for review, not scheduled" tells the agent when this tool is the right choice versus a scheduling tool like schedule_post, and the persona_id omission rule gives clear usage context. It stops short of naming alternatives or stating prerequisites such as needing an existing persona.

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