cowpin_save_memory

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'automated text extraction', 'OpenGraph metadata parsing', and '1536-dimensional vector embeddings', which gives some insight into processing. However, it does not disclose side effects, error conditions, what happens when both url and content are supplied, or any authentication requirements. The description provides moderate transparency but leaves important behavioral aspects unstated.

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 a single sentence that is front-loaded with the primary purpose and then lists processing features. There is no redundancy or filler; every clause contributes to understanding the tool's role.

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 6-parameter tool with no annotations and no output schema, the description provides a solid overview but omits details on parameter interactions (e.g., precedence of url vs content) and any return behavior. It does not mention whether tags or notes are required or how they are stored. The description is sufficient for a basic understanding but leaves gaps that could affect correct invocation in edge cases.

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%, so the baseline is 3. The description adds meaning by clarifying that url and content are alternative input modes ('or'), and it hints at processing applied to the url (text extraction, OpenGraph). This goes beyond the schema's simple field descriptions and helps the agent understand how parameters are used together.

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 tool's function: 'Save a webpage URL or raw text/markdown notes into the persistent Cowpin memory vault' and lists specific processing capabilities (text extraction, OpenGraph metadata parsing, vector embeddings). It distinctly differentiates itself from sibling tools that search or retrieve memories.

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 implies usage for storing new memories but does not explicitly contrast with search or retrieval tools. There is no guidance on when not to use it, such as when an existing memory should be updated or when to prefer cowpin_search_memory. The usage context is clear but lacks explicit exclusions or alternative routing.

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