trove_add_snippet

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

No annotations provided, so description carries the full burden. It discloses the file path structure, that the tool rebuilds the index after saving, and hints at side effects via the overwrite parameter. It could mention more about slug derivation or frontmatter format, but the key behaviors are covered.

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 sentences, no filler. First sentence defines the core action and destination; second provides a critical formatting instruction. Every word earns its place.

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?

With 8 parameters and no output schema, the description explains the key path logic and body formatting. It doesn't detail the frontmatter structure or slug derivation, but these are implied by Markdown conventions. The tool's complexity is moderate, and the description covers the essential usage aspects.

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 baseline is 3. The description adds value by explaining how parameters combine into a path (snippets/<domain>/<subpath>/<slug>.md) and by constraining body_markdown to be pre-segmented. This provides meaning beyond the schema's simple property 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?

Description clearly states the action (save a plaintext snippet), the resource (Markdown with frontmatter), and the destination path pattern (snippets/<domain>/<subpath>/<slug>.md). It distinguishes itself from sibling tools like trove_add_secret by focusing on code snippets.

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 gives explicit formatting guidance for body_markdown ('already segmented (prose outside fences, code in fenced blocks)'), which helps proper use. However, it does not explicitly state when to use this tool versus alternatives like trove_add_secret, though the purpose is clear enough from context.

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