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

Annotations already cover the safe-read profile (readOnly, idempotent, non-openWorld), and the description adds genuinely non-obvious behavior beyond them: identity fields are null on anonymous projects, respondent filters fail with a 400, and answer text is untrusted community content. That is exactly the kind of surprising-failure-mode and safety context annotations cannot convey.

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?

Three tight sentences with the core purpose front-loaded, followed by the two highest-value caveats. Every sentence earns its place and nothing is redundant.

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 paginated list tool with no output schema, the description covers privacy semantics and the filter failure mode well. It omits the return shape (a collection of responses) and pagination behavior, which the absent output schema leaves undocumented, so a small gap remains.

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 page, user_id, provider, platform_id, session_number, and project_id are all documented in the schema itself. The description references "respondent filters" generically but adds no format, default, or interaction detail beyond the schema, so the baseline 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 opens with a specific verb+resource ("List a project's responses"), which cleanly separates it from the singular get_response and the delete_response(s) siblings. It does not explicitly name an alternative tool or state when not to use it, so it stops 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?

Usage is implied by the listing scope, and the note that respondent filters return 400 on anonymous projects is operationally useful. However, there is no explicit when-to-use guidance or routing to siblings like get_response for a single record, leaving the agent to infer.

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