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

Annotations supply the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the agent knows calling it may have side effects but is repeatable. The description's 'get or generate' is broadly consistent with a non-read-only tool, but it never clarifies whether a summary is persisted, how costly generation is, or when generation is triggered.

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?

A single short sentence with no filler and the action is front-loaded. It is efficiently sized, though its brevity comes partly from underspecification rather than tight editing.

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 not be explained. However, the central ambiguity of get-vs-generate and the side effects implied by readOnlyHint=false remain unaddressed, leaving the description only minimally adequate for this 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 description coverage is 100%, including the default/max for message_count and the purpose of target_session, so the schema already carries parameter meaning. The description adds nothing beyond that, which is the baseline 3 when the schema does the heavy lifting.

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 verb and resource (summarize/get a summary of a conversation), but the dual 'get or generate' phrasing is vague about what actually happens on a call. No differentiation from siblings like query or manage_chat is offered, so an agent can't tell when this is the right tool.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives. The description gives no signal about whether this is for fetching an existing summary versus triggering generation, which is exactly the decision an agent must make.

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