summarize_conversation

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not say whether summaries are cached or freshly generated, whether generation is expensive/slow, what happens when no summary exists, or whether an existing summary is overwritten when regenerated. For a dual-mode "get or generate" tool this is a meaningful gap, though it does not contradict the readOnly annotation.

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 padding and no buried information. It is efficient, though the brevity is partly achieved by omitting behavior rather than by 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?

With annotations covering the read-only/open-world profile and a fully documented schema, the remaining burden on the description is modest. Still, the get-vs-generate distinction, cost/latency implications, and any caching behavior are unaddressed, which is the one thing an agent most needs to know here.

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%, so all three parameters (conversation_id, message_count, target_session) are already fully documented with defaults, bounds, and meaning. The description adds no parameter-level meaning beyond the schema, which is the expected baseline 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?

The verb+resource pair (summarize a conversation) is identifiable, and it is not confusable with siblings like get_analytics or query. However, "Get or generate" leaves a real ambiguity: it is unclear whether this is a pure read of a cached summary, a request that triggers generation, or both depending on state. That ambiguity is central to what the tool does, so this lands at minimum-viable rather than clear.

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 when-not-to-use, and no mention of any sibling tool (e.g. get_analytics, query) that might compete for the same intent. The agent must infer that this is the right tool purely from the name.

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