Send Create

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

Description adds context about creation behavior (Quick-create), deletion/access controls, and optional password protection. Annotations provide readOnlyHint=false and destructiveHint=false, which align with the description. No contradictions.

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 tightly focused sentences. First covers core functionality and type-specific parameters; second directs to alternatives. No 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?

Covers main creation aspects and optional parameters well. Lacks return value info but given no output schema, it's acceptable for a creation tool. Notes necessary parameter dependencies.

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%, baseline 3. Description adds meaning by grouping parameters by type (text vs file) and explaining control parameters like deleteInDays, maxAccessCount, and password.

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?

Description clearly states 'Quick-create a Bitwarden Send' and specifies the two types (text/file) with their required parameters. It distinguishes from sibling tools send_create_encoded and send_edit by noting they are for advanced JSON templates or edits.

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 tells when to use which type and parameters. Directs to alternatives for advanced cases: 'For advanced JSON templates or edits, use send_create_encoded and send_edit instead.'

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