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

Annotations already declare readOnly=false, destructive=true and idempotent=true, and the description adds real substance on top: one entry per round, re-saving updates rather than duplicates, and only passed fields change. It stops short of stating that removals via clear_fields or tags replacement are irreversible, which matters given destructiveHint=true.

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 tight sentences: prerequisite, purpose, update semantics, sibling routing. Front-loaded with the gating requirement and no filler or repetition of the title.

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?

For a 12-parameter mutation tool with rich annotations, the description covers auth, upsert behavior, partial updates and sibling routing, which is most of what an agent needs. With no output schema, it could still say what the call returns or whether the saved entry is echoed back.

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 per-field meaning (omit to keep, empty string clears, tags replace, clear_fields by name) is already fully documented in the schema. The description reinforces the partial-update model and the round-vs-application distinction for interview_id, but adds little beyond what the schema already says.

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 specific verb and resource ("Records the user's lessons learned for an interview round, or for a whole application") and enumerates the content captured (questions, went well, improve, red flags, next prep, confidence, tags). It also explicitly separates itself from log_interview, so an agent can route correctly 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 an explicit when/when-not split: record reflections here, while "the round's time and result belong in log_interview." It also states the sign-in prerequisite up front, so the agent knows the call is user-scoped.

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