crm_outbound_messaging

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

No annotations provided; description implies it drafts messages but does not clarify if it actually sends them or just generates text. Missing details on auth requirements, rate limits, or side effects. The behavioral scope is partially described but insufficient.

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?

Well-structured with a purpose paragraph followed by a bullet-like Args list. Front-loads the main action. Could be slightly more concise, but no wasted sentences.

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?

Output schema exists but description does not mention return value (e.g., drafted message). Lacks prerequisites (e.g., contact must exist). Adequate for a drafting tool but missing some context.

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 has 0% description coverage, so description carries full burden. It lists all 5 parameters with concise explanations, including valid values for 'channel' (email, linkedin, sms) that are not in schema enums. Could improve with format or constraints for 'intent' and 'tone'.

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 clearly states it drafts a personalized outbound message (cold email, LinkedIn, etc.) for prospects, specifying the context (ICP, value props, role, recent activity). It distinctly separates itself from other CRM tools like crm_book_meeting or crm_enrich_contact.

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?

No explicit guidance on when to use this tool versus alternatives. The description lacks 'when to use' or 'when not to use' instructions, and does not compare with sibling tools.

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