Synapse

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

The description adds valuable behavioral context beyond annotations: it explains the dual behavior (URL fetching vs direct content saving), mentions frontmatter addition, and specifies the default folder. Annotations already indicate this is a non-readonly, non-destructive, non-idempotent operation with open-world data, but the description provides practical implementation details.

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 efficiently structured in three sentences: first states purpose and use case, second explains the dual input behavior, third mentions frontmatter addition. Every sentence earns its place with no wasted words, and key information is front-loaded.

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 content-saving tool with no output schema, the description provides good context about behavior and use cases. However, it doesn't mention error conditions, file naming conventions, or what happens when both url and content are provided. Given the annotations cover safety aspects and schema covers parameters well, this is reasonably complete.

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?

With 100% schema description coverage, the schema already fully documents all 4 parameters. The description mentions URL fetching/conversion and direct content saving, which aligns with the url and content parameters, but doesn't add significant semantic value beyond what's in the schema descriptions. Baseline 3 is appropriate when schema does the heavy lifting.

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 specific action ('save content to the vault's sources folder') and distinguishes it from siblings by specifying the target folder and use case for mobile users. It explicitly differentiates from web clipper tools and other vault operations like read, write, or search.

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 context about when to use this tool ('ideal for mobile users who find articles and want to save them without a web clipper'), but doesn't explicitly state when NOT to use it or name specific alternatives among the sibling tools. It implies usage for saving content from URLs or direct input.

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