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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the tool's safe, non-mutating nature is well established. The description adds that it converts example pairs into formatted blocks, which is largely synonymous with its purpose and provides minimal extra behavioral context beyond the annotations.

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 concise, with two sentences that are front-loaded with the core purpose. It lists the supported formats without wasting words, making it easy to scan and understand.

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?

The description covers the tool's main inputs and outputs, and the schema and annotations provide the rest. Since the tool is relatively simple and has high schema coverage, the description is sufficiently complete for an agent to use it correctly, though it could theoretically include an example of the output format.

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 input schema has 100% coverage, with descriptions for all four parameters including enum values for format. The description only repeats the format options and mentions example pairs, adding little beyond the schema. Per the baseline for high schema coverage, this is adequate but not exceptional.

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 description clearly states the tool's purpose: formatting few-shot examples for LLM prompts. It specifies the action (format/converts), the resource (few-shot examples), and the supported output formats (chat, XML, Markdown, plain text), which distinguishes it from sibling formatting tools.

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 implies usage context by stating it formats few-shot examples for LLM prompts, which is clear enough for most users. However, it doesn't explicitly mention alternatives or when not to use this tool, but the context is sufficient given the sibling list.

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