create_message_draft

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

No annotations are provided, so the description carries full burden. It does not disclose whether the draft is saved, whether it sends anything, whether authentication is required, or what happens upon success. It only states the action and parameter meanings, leaving significant behavioral aspects undisclosed.

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?

The description is compact, leading with the purpose sentence and using a concise 'Args:' block to define parameters. Every sentence adds information without 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?

The output schema exists, so return values need not be described. The parameter meanings are covered, but the description lacks behavioral context (e.g., draft lifecycle) and usage guidance, making it complete only for the simplest operation level.

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?

The schema has no descriptions (0% coverage), but the description lists each parameter with a brief meaning: subject, body, and to (with comma-separated recipient format). This adds functional meaning beyond the schema titles. However, it doesn't provide details like validation rules or optionality nuances beyond the required fields.

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 description uses the imperative verb 'Create' with the specific resource 'a draft message' and target 'Nimble CRM', clearly distinguishing it from sibling tools like list_message_drafts which retrieves drafts. It is specific and unambiguous.

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?

It implies usage (when you need to create a draft message) but does not explicitly mention when not to use it or suggest alternative tools. No exclusions or alternative references are provided.

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