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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only the underlying endpoint ("GET /survey_responses"), which is mild context; it says nothing about pagination behavior, volume, or auth needs beyond what the schema's page parameter already conveys.

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 tight fragments with the core action front-loaded and the filter dimensions immediately after. Nothing is redundant and there is no 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?

For a read-only list tool with no output schema, annotations covering safety, and full schema coverage, the description is minimally adequate. It omits any mention of the date-range filters (created_after/created_before) and pagination, which are meaningful capabilities of this endpoint, so it falls short of complete.

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 100%, so all six parameters are self-documenting in the schema. The description references three of the filter dimensions (survey, email, subscriber) but adds no syntax, semantics, or defaults beyond the schema. 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?

States a specific verb+resource ("List survey responses") and clarifies the payload with "(who answered what)", so an agent knows this returns individual answers rather than survey definitions. It doesn't explicitly name the sibling buttondown_list_surveys to differentiate the two, which keeps it short of a 5.

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?

"optionally for one survey, email or subscriber" implies the filtering contexts in which this tool is useful, but there is no explicit when-to-use, when-not, or named alternative. The usage signal is inferable rather than stated.

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