get_responses

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

With no annotations provided, the description carries the transparency burden. It discloses that the tool returns full conversation threads and warns about large data volume, but it does not mention side effects (e.g., read-only nature), pagination behavior, or error conditions. This is adequate but not rich.

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 two sentences, front-loaded with the primary purpose, followed by return characteristics and practical guidance. Every sentence adds value with no redundancy or filler.

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 gives a clear purpose and performance tip, but it does not fully clarify the relationship between 'participant responses' and 'full conversation threads', nor how the filters map to the response data. It is adequate given the rich schema, but leaves some ambiguity about the data structure and tool boundaries.

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% description coverage for all 6 parameters, including filter semantics. The tool description itself does not add detail about individual parameters, so it neither enhances nor detracts from the schema's explanations. Baseline of 3 applies.

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 retrieves participant responses for a Harmonica session and returns full conversation threads. It specifies the resource and action, distinguishing it from list_participants and get_summary. However, it does not explicitly name alternative tools for comparison.

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 provides clear context by recommending the use of filters to avoid fetching all data at once for large sessions. This implies a performance consideration but stops short of explicit when-to-use vs. alternative tools or exclusions.

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