Send Create (Encoded JSON)

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

Annotations already provide readOnlyHint=false, destructiveHint=false, openWorldHint=true. Description adds context like file composition and hidden affecting only text sends. However, it does not disclose side effects (e.g., send creation triggers notifications) or return value, given openWorldHint suggests broader impact.

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?

Three sentences, each contributing distinct value: main purpose, input modes, and usage guidance. No redundancy, front-loaded with key action, efficient.

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?

Despite complexity (5 params, nested file object, no output schema), description does not mention return value (expected send object) or potential side effects from openWorldHint. Lacks output specification but covers input modes and usage well.

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 coverage is 100% with descriptions. Description adds structural grouping (encodedJson/json vs text/file) and clarifies that 'hidden only affects text Sends' – information not fully captured in schema. This enhances understanding of parameter relationships.

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?

Clearly states 'Create a Send with the advanced bw send create flow' – specific verb and resource. Distinguishes from sibling keychain_send_create by noting 'beyond the quick send_create options'. Lists input modes (encodedJson, json, text, file).

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?

Explicitly states when to use: 'Use this when you need template-level fields beyond the quick send_create options.' Implicitly identifies keychain_send_create as alternative. Also breaks down input method alternatives.

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