Receive

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

Annotations already declare readOnlyHint and openWorldHint. The description adds context about reading a shared Send without modifying vault items, and explains the three output modes (text, JSON object, file download). No contradictions with annotations.

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 concise with two sentences, no wasted words. It front-loads the core action and then details options and constraints.

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 no output schema, the description thoroughly explains the three possible return types (text, JSON object, file details) and when each applies. It covers the required param and optional parameters sufficiently for correct tool invocation.

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?

Input schema has 100% description coverage for all 4 parameters. The description adds value by explaining the behavior of obj and downloadFile parameters beyond their schema descriptions, clarifying that obj returns parsed JSON and downloadFile returns base64 bytes.

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 'Receive a Bitwarden Send from an HTTPS url,' specifying the resource (Bitwarden Send) and action (receive). It distinguishes from siblings like keychain_send_create and keychain_send_delete, which handle creation or deletion.

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?

The description explains when to provide a password and the effects of obj and downloadFile parameters. It also clarifies that the tool only reads and does not modify vault items, guiding appropriate usage. However, it does not explicitly mention when not to use it or list alternatives.

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