create_memory

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

With no annotations, the description must fully disclose behavioral traits. It only mentions parameter constraints (already in schema) and that the memory is stored durably. It omits side effects, required permissions, reversibility, or any nuance beyond creation.

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 extremely concise with two sentences, no wasted words. However, given the tool's complexity (7 parameters), it may be overly minimal, but it remains efficient.

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?

Despite an output schema existing, the description fails to provide context on invocation order, prerequisites (beyond 'confirming'), or when to use this tool. For a creation tool with 7 parameters and no annotation help, it is incomplete.

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 only 14%. The description repeats enum values for confidence and auto_prefetch_level that are already defined in the schema, adding no new meaning. No explanation is given for the other five parameters (body, tags, title, summary, category_id).

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 tool creates a 'Glyph Hold memory' with the verb 'create', unambiguously identifying the resource and action. It does not conflict with sibling tools like create_secret (different resource) or search_memories (different action).

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 phrase 'after confirming it should be stored durably' implies a prerequisite but does not provide explicit guidance on when to use this tool versus alternatives like create_secret or search_memories. No when-not or exclusion criteria are given.

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