Prepare a conversation for another system

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

The description explicitly states that the tool never sends anything, making its non-destructive and read-only nature unmistakable. It also reveals what the return payload contains (the exact call and unfillable required fields), matching the readOnlyHint annotation and going beyond it.

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 tight and efficient, using three sentences to convey purpose, behavior, and recommended follow-up action. There is no redundant or filler content.

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?

Given the read-only annotation and the simple parameter set, the description covers the main behavior, output contents, and side-effect expectation. It is slightly incomplete in explaining the meaning of each parameter, but overall it gives enough context to use the tool safely and correctly.

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 schema has no parameter descriptions and the description does not individually explain conversationId, target, tool, or shape. With 0% schema coverage, the description needed to compensate by explaining these parameters, but it only indirectly refers to 'conversation' and 'downstream MCP tool.'

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?

Clearly states a specific action: maps a conversation onto a downstream MCP tool's input schema and returns the would-be call, including missing required fields. It also explicitly distinguishes itself from actually sending by saying it never sends anything, which separates it from sibling 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?

Explains when to use it: to review a prepared payload before executing it with the downstream tool. It even instructs the agent to make the call itself if execution is desired, providing practical usage guidance. It does not explicitly name sibling tools, but the guidance is clear enough.

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