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

The annotations already declare readOnlyHint=true, which is consistent with the described wait operation. The description adds meaningful context beyond annotations by specifying the return format ('Returns the same format as convoreply when successful') and clarifying that it does not resend the message, which enhances transparency about the tool's runtime behavior.

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 well-structured and front-loaded: the first sentence states the purpose, followed by a clear 'USE THIS TOOL WHEN' section, then required/optional parameters, and a return format note. Every line serves a purpose with no redundant content, making it concise yet comprehensive.

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 tool's simplicity (3 parameters, no output schema), the description covers essential aspects: purpose, trigger, requirements, timeout limits, and return format. A minor gap is lack of guidance on repeated timeouts, but the read-only/open-world annotations and sufficient detail make it complete for most agent decision-making.

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 coverage is 100%, so all three parameters are already thoroughly described in the input schema (e.g., timeout max, session_id pattern). The description organizes them into REQUIRES/OPTIONAL and repeats the same context from the schema, adding little new semantic value beyond the structured definitions.

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 action: 'Wait for a pending response from Riley after a convoreply timeout.' This is a specific verb ('wait') with a clear resource and trigger, and it distinguishes itself from convoreply by noting 'without resending the message,' making the purpose unambiguous and differentiated.

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 explicitly provides a usage condition: '🎯 USE THIS TOOL WHEN: convoreply returned a timeout error.' It also explains the benefit ('continue waiting... without resending') and outlines prerequisites and optional parameters, giving clear guidance on when to use it versus alternatives.

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