memory_apply_template

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

With no annotations, the description must disclose behavioral traits. It states 'apply a template's rules/memories into a project' but does not specify whether this merges or overwrites existing content, whether it is idempotent, or what permissions are required. The vague verb 'apply' leaves critical behavior unspecified.

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 a single brief sentence, which is efficient. However, it sacrifices necessary detail for brevity. It is front-loaded with the verb but lacks substantive information.

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?

Given the existence of an output schema (unknown content) and two parameters, the description is insufficiently complete. It does not explain return values, side effects, or how the template is applied. The tool is part of a large ecosystem, but the description provides minimal context.

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 0%, yet the description does not explain the parameters. The template parameter is mentioned only as 'by template name' with no format or constraints. The project parameter is completely ignored. This fails to add meaning beyond the basic schema definition.

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 verb 'Apply' and identifies both the resource (template's rules/memories) and the target (project). It distinguishes from other memory tools like memory_add_template_rule or memory_list_templates. However, 'by template name' is slightly ambiguous—it could mean the template identifier is a name, but the schema confirms template is a string.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., memory_add_template_rule, memory_create_template). There is no mention of prerequisites or context for application.

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