send_conversation_reply

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

Discloses that the tool triggers a stateful action (openWorldHint=true) and requires polling for AI response, adding value beyond annotations. However, does not detail rate limits, authentication needs, or potential delays.

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?

Two concise sentences: one for purpose, one for next step. No redundant or vague phrasing; efficient and clear.

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?

Tool is straightforward and the description, combined with annotations and output schema (not shown but present), covers key behavioral aspects. Explains the polling pattern, which is critical for correct usage.

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?

Input schema covers 100% of parameter descriptions, so the description adds no additional parameter semantics. Baseline 3 is appropriate.

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 action (send a user reply) and context (ongoing conversation, interview or table-maker). Distinguishes from sibling tools like get_conversation and wait_for_conversation, which serve different purposes.

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 instruction to poll get_conversation after sending, guiding the agent on the expected workflow. Lacks explicit when-not-to-use or alternatives, but for a focused tool this is sufficient.

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