Export all snippets and folders as JSON

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe read-only behavior is covered. The description adds the authenticated-user scope and JSON output format, but does not disclose response structure, size limits, pagination, or any other behavioral detail. This is adequate but somewhat minimal.

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 short and front-loaded, with the core action stated in the first sentence. The second sentence largely restates the first and adds only the authenticated-user scope, so there is minor redundancy, but it remains compact and easy to parse.

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 zero-parameter, read-only export tool, the description covers what is exported, for whom, and in what format. There is no output schema, so some detail about the JSON structure could be helpful, but the description is sufficient for an agent to confidently select and call this tool for a bulk export.

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 tool has zero parameters, and the schema coverage is effectively 100%, so there are no parameter semantics for the description to clarify. The description usefully reinforces that the export covers all snippets and folders with no filtering options. Baseline 4 is appropriate for a no-parameter tool.

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 states a specific verb (export), a specific resource (all snippets and snippet folders), and an output format (JSON). It also clarifies the scope is the authenticated user's data. However, it does not explicitly distinguish itself from sibling tools like get_all_snippets or get_all_snippet_folders beyond the bundled 'snippets and folders' scope.

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 this tool is for retrieving a full JSON export of snippets and folders for the authenticated user. It does not explicitly say when to use it instead of the sibling get_all_snippets/get_all_snippet_folders tools, nor does it describe exclusions or alternatives. The usage context is clear but not elaborated.

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