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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds meaningful behavioral detail by specifying the exact output structure for both text and JSON formats, which goes beyond the schema. No contradictions.

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?

The description is two sentences with no filler. The purpose and use cases are front-loaded, followed by concise format examples. Every sentence adds useful information without redundancy.

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 simple read-only export tool with one parameter and no output schema, the description fully covers what it does, when to use it, and what the output looks like. Nothing an agent needs to correctly invoke it is missing.

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?

The single parameter 'format' is already fully described in the schema (enum with 'text' default and 'json' for structured data), so schema coverage is 100%. The description adds extra value by detailing what each format contains (e.g., '[Speaker] Content' lines and message object fields like id, timestamp, author, etc.), which is not in 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 specific verb (export) and resource (full chat log), and specifies the two output formats (text/JSON). It clearly separates itself from siblings like chat-list and chat-get by emphasizing 'full chat log' and 'export' rather than listing or retrieving individual messages.

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?

Provides explicit use cases ('session summaries, recapping what happened, saving chat history') which helps an agent decide when to invoke it. However, it does not name alternative tools or state when not to use it, leaving some inference required given the many chat-related siblings.

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