Create conclusion

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

With no annotations, description adds context about durability and priority, but fails to disclose idempotency, overwrite behavior, or side effects. Partially transparent but incomplete.

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?

Single sentence, front-loaded purpose. Efficient but could benefit from structured sections (e.g., usage notes) to improve scannability without adding length.

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 5 parameters, no output schema, no annotations, and many sibling tools, the description is incomplete. It lacks return value info, parameter clarifications, and differentiation from other memory tools.

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?

Only 'text' has schema description; other parameters (tags, source, expiresAt, namespace) have zero description. The tool description does not compensate, leaving most parameter semantics ambiguous.

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?

Specifies verb 'save' and resource 'conclusion/preference', distinguishes from raw memory with 'higher-signal'. However, does not explicitly differentiate from sibling tools like 'remember' or 'list_conclusions'.

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?

Implies conclusions are durable and higher-signal, but lacks explicit guidance on when to use this tool versus alternatives (e.g., 'remember' for basic memory). No when-not or exclusion criteria.

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