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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds the useful default of a 30-day window and the fields returned, but says nothing about result caps, pagination, or ordering for a potentially large response set.

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 compact sentences plus an endpoint path; the core purpose and the field list are front-loaded. The raw 'GET /api/survey/{uuid}/responses.json' adds little for an MCP caller and is the one element that does not fully earn its place.

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 output schema, the description does the right thing by sketching the returned fields, and read-only annotations cover the safety profile. Missing pagination/size expectations for a responses listing, but otherwise complete for a simple filtered read.

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 the baseline is 3; however, the description contributes information the schema lacks — the default date range when start_date/end_date are omitted. That is genuine added meaning for the two optional date parameters, though formats are left to the schema.

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?

States a specific verb and resource ('List the responses to one survey') and even enumerates the payload fields (ratings, follow-up text, contact, tags). It is readily distinguished from textline_list_surveys, though it never names that sibling, so differentiation is implicit rather than explicit.

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?

Usage is implied: you call this when you have a survey UUID and want its responses, and the 'Default: the last 30 days' note tells the agent what happens if the date params are omitted. There is no explicit when-not guidance or named alternative (e.g., textline_list_surveys for discovering UUIDs), so it stops short of a 4.

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