log_conversation

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

Goes well beyond the annotations by explaining why the call is needed (direct-to-model clients record nothing), that already-sent lines are skipped, and that the returned conversation_id must be passed back to enable that dedup. It also states the return shape, which no output schema provides. This is behavioral context the readOnly/idempotent hints cannot convey.

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?

Front-loads the purpose and keeps the operational rules (timing, trimming, dedup, skip condition) tight and scannable. The opening framing about diaries and memories is slightly conversational, but no sentence is genuinely wasted.

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 everything an agent needs: motivation, timing, exclusion, alternative tool, payload hygiene, dedup protocol, and the exact return fields, compensating for the absent output schema. Nothing material is missing for a 3-parameter write tool.

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 is 3, but the description adds real semantics: messages must be ordered oldest-first, trimmed of code and pasted documents, and conversation_id must be carried forward from the first call. Only `namespace` is left entirely to the 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?

States a concrete action (hand the conversation to the nightly memory pass so it becomes diary memories) rather than restating the name. It also distinguishes itself from the sibling `remember` by contrasting deferred logging with immediate recall, so an agent can pick between them without opening either schema.

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?

Gives explicit timing (when the conversation winds down, every ~20 exchanges in a long one), an explicit exclusion (skip it when the Aelios gateway auto-adds memories each turn), and an explicit alternative (`remember` for anything that matters right now). Both when and when-not are covered.

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