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

Annotations carry destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the mutation profile is already declared. The description adds genuinely new behavioral constraints the annotations cannot express: write the summary yourself, do not paste the raw transcript, and never include credentials. It stops short of explaining the overwrite-on-same-key behavior, which lives in the schema instead.

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?

Three tight sentences, front-loaded with the action and its payoff before the content rules. The section list is dense but each item earns its place as a content requirement rather than filler.

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?

An output schema exists, so return values need no explanation, and the description fully specifies what to put in the required content field. Gaps remain around the update-in-place semantics and the platform/model/tags parameters, but the core write path is adequately specified.

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 only 43%, so the description must compensate. It does clarify the content parameter (a self-authored Markdown handoff covering objective, decisions, state, artifacts, next steps, constraints), which is real added meaning, but tags, model, title, and messageCount remain undocumented anywhere.

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?

Specific verb (save) plus resource (handoff summary to CortexPlus memory) and an explicit downstream purpose (resume in another AI platform). An agent can distinguish this from siblings like remember, memory, recall, and resume without opening any 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?

The description establishes the context of use ('so it can be resumed later in another AI platform') and gives content rules, but never names or contrasts the neighboring tools (remember, memory, resume) that an agent might confuse this with. Clear context, no explicit alternatives.

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