project_template_save

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

Discloses return structure, side effects (writes folder+project, sets syncPending), and metadata format. Lacks explicit statement that original project is unmodified, but overall good coverage given no annotations.

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?

Four concise sentences front-loaded with main action, followed by structure, guidance, return/side effects, and example. No fluff, every sentence 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?

Covers return value, side effects, folder location via env var, and example. Does not address templateName uniqueness enforcement or ID format, but given low complexity, it is nearly 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?

Schema coverage is 100%, so baseline 3. Description repeats schema descriptions for parameters but adds contextual example showing usage of templateName and parameterNames. No new semantic insight beyond schema.

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 tool captures a project as a reusable template, naming the folder location. It distinguishes from sibling task_duplicate, making the purpose specific and unambiguous.

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?

Explicitly instructs not to use for one-off duplication and directs to task_duplicate, providing clear when-to-use and when-not-to-use guidance. Implies appropriate context for template creation.

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