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

Annotations declare a non-destructive, closed-world write; the description goes beyond that by confirming 'Nothing is sent' (no external side effect) and disclosing that sender and template are chosen automatically, which is real behavioral context. It still omits whether a persistent draft record is created or how an existing draft is handled.

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, front-loaded sentences with zero filler; the essential constraint ('Nothing is sent') is placed where it will be read immediately.

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 four-required-parameter write tool with no parameter documentation and no output schema, the description leaves too much unsaid: no explanation of the ID parameters, no prerequisites, and no note on what is produced (draft location/state). Adequate for identifying the tool's intent, insufficient for invoking it confidently.

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 nothing in the description explains projectId or siteId, two of the four required IDs. The phrase 'a prospect's contact' weakly implies prospectId and contactId, but half the parameters remain undocumented in both the schema and the description.

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 first email to a prospect's contact') and adds a differentiating detail — Ranklybee auto-selects the sender and template. This distinguishes it conceptually from explicit-selection siblings, but it never names create_outreach_draft or regenerate_outreach_draft, so the agent must infer which of the very similar draft tools applies.

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?

'First email' implies the initial-touch use case, implicitly contrasted with send_outreach_follow_up. However, there is no explicit when-to-use-vs-alternative statement covering create_outreach_draft, update_outreach_draft, or regenerate_outreach_draft, and no stated prerequisites (e.g., contact verification).

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