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

With readOnlyHint=false, the description goes beyond the annotation by specifying the persistence target ('Second Brain'), the ownership restriction ('Only the author's own draft can be saved'), and the return value ('Returns the saved_template_id'). It doesn't mention overwrite behavior or error cases, but for a simple save operation this is solid context.

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?

Three efficient sentences with the core action front-loaded, followed by input requirements and a constraint. No filler or redundant explanation.

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 low-complexity write tool with two fully documented parameters and no output schema, the description provides everything needed to invoke it correctly: inputs, scope, restriction, and return value. Minor gaps like duplicate-name behavior or error handling don't materially hinder correct use.

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 description coverage is 100% and both parameters are documented. The description adds some nuance ('artifact_id a generator returned', 'a short name the user would recognise') but largely repeats the schema's meaning, so it doesn't elevate above the baseline.

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 ('Save') and resource ('generated image, email or PDF as a template in the user's Second Brain'), making its purpose clear and distinct from sibling generators and list_templates. However, it doesn't explicitly name any sibling or contrast itself, so it isn't a full 5.

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?

It clearly establishes the usage context: after a generator returns an artifact_id, and with the constraint that only the author's own draft can be saved. This tells an agent when the tool applies without explicitly listing when-not-to-use or naming alternative tools.

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