Send Get

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

Annotations already declare readOnlyHint=true, so the tool is understood to be non-destructive. The description adds that setting 'text=true' returns text content and 'downloadFile=true' downloads a file, which is useful but does not disclose additional behavioral traits beyond what annotations and schema imply.

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 extremely concise, consisting of two sentences with no extraneous information. The first sentence clearly states the purpose, and the second provides actionable usage tips for the optional parameters.

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?

For a simple get tool with strong annotations and full parameter schema coverage, the description is mostly complete. However, it does not explain the default behavior when neither 'text' nor 'downloadFile' is specified (presumably returning JSON metadata), which could be inferred but is not explicit.

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?

All three parameters are fully described in the input schema (100% coverage). The description adds value by clarifying the behavioral effects of 'text' and 'downloadFile' parameters, going beyond the schema's basic type descriptions.

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, and the inclusion of 'text' and 'downloadFile' flags further specifies its function. However, it does not explicitly differentiate from keychain_send_list, which lists all sends, leading to slight ambiguity about whether it retrieves a single send or multiple.

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 guidance is provided on when to use this tool versus alternatives like keychain_send_list. The description only mentions the optional flags, but does not discuss prerequisites, exclusions, or comparison with sibling tools.

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