speak_when_done

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

No annotations provided, so description carries full burden. It transparently describes the tool's behavior: it speaks a summary out loud, is conversational, and should be called at the end. 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?

Description is clear and front-loaded with the core action. It consists of four sentences, each adding value. However, could be slightly more concise by combining the second and third sentences.

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 no param explanations and no output schema needed, the description covers the usage intent well but lacks details on parameters and potential limitations like language or audio length, which would help with complete context.

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 0%. The description does not explain the parameters (text, voice, speed) at all. It only describes what the tool does in general terms, leaving the agent without guidance on how to populate the fields.

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?

Description clearly states the tool speaks a brief summary out loud at the end of every response. It specifies the verb 'speak' and the resource 'summary of your response', with clear usage context.

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?

Explicitly instructs to call at the end of EVERY response, and provides guidance on content: summarize in 1-3 sentences, shorten if possible, and speak only the question if the response is a question. No sibling tools to differentiate.

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