Send Get

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

Annotations already declare readOnlyHint=true and openWorldHint=true. Description adds 'owned by you' but does not elaborate on traits like error handling or rate limits. Adds minor value beyond 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?

Description is one sentence with two clauses, efficiently covering the main purpose and optional flags. No wasted words, though could be slightly more structured.

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?

Given the simple tool with few parameters and no output schema, the description adequately explains the get operation and optional flags. It assumes the user knows id is required (covered by schema), but doesn't mention default behavior when no flags set. Good enough for this complexity.

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 for each parameter. The description repeats the parameter purposes ('text=true to return text content; downloadFile=true to download a file send') without adding new semantic depth beyond the schema. Baseline 3 applies.

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 gets Sends owned by the user, with options for text content or file download. It distinguishes from sibling tools like keychain_send_list and keychain_send_create by specifying retrieval of a single Send with flags.

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?

Provides guidance on using text=true and downloadFile=true for specific cases, but does not explicitly compare to alternatives like keychain_send_list for listing all Sends or keychain_send_edit for modifications. Implicit context but lacks explicit when-not-to-use.

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