Send Edit (Encoded JSON)

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

Description indicates mutation (edit) and mentions encoding process but omits details like permissions required, side effects, or failure modes. Annotations already flag non-read-only, so description adds moderate context.

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 concise sentences that front-load the core action and then cover parameter options. No unnecessary words.

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?

Adequately covers input encoding and optional parameter, but missing information about return values or success indications. Since no output schema exists, a brief note on response would improve completeness.

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?

Explains the relationship between encodedJson and json (raw json is encoded before invoke) and clarifies itemId maps to --itemid. Adds meaning beyond schema 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?

Clear verb 'Edit' with resource 'existing Send'. Distinct from sibling tools like keychain_send_create, keychain_send_delete, etc., making purpose unambiguous.

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?

Mentions 'advanced bw send edit flow' but does not specify when to use versus alternatives or provide exclusions. Lacks guidance on prerequisites or context.

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