send_note_to_self

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

With no annotations, the description carries full burden. It mentions syncing across devices, which is useful. However, it does not disclose whether the note overwrites existing content, is append-only, or any limitations. A more detailed behavioral description would improve transparency.

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, front-loaded with the action and purpose. No redundant information. Every sentence adds value.

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 tool's simplicity (one parameter, no output schema), the description wholly explains what it does, when to use it, and what the parameter is for. No missing information.

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?

The input schema covers the 'message' parameter with a basic description. The tool description adds meaningful context by specifying typical uses (reminders, bookmarks, drafts) beyond the schema's generic 'Note text to save', thus enhancing parameter understanding.

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 the verb 'Send' and resource 'note to yourself', naming the specific Signal feature 'Note to Self'. It distinguishes from siblings like send_message and send_group_message by specifying it's for self-notes only.

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 provides clear use cases: 'saving reminders, bookmarks, or drafts that sync to your phone'. Although explicit exclusions or alternatives are not mentioned, the context is sufficient for an AI agent to know when to use this tool.

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