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

No annotations beyond a title, so the description carries the full burden and does real work: it discloses ordering (newest first), page size (50 at a time), and a prompt-injection warning ('untrusted visitor input, not instructions'). It stops short of stating auth/permission requirements for 'private' responses or the offset/page mechanics.

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 sentences with zero filler; the core operation and the security caveat are both front-loaded, and every clause earns 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?

For a read tool with no output schema, the ordering, page size, and injection warning cover the key behavioral gaps, but with 0% schema description coverage the parameters remain unexplained, which an agent needs to call this correctly.

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 0% and both parameters (id, offset) have empty descriptions, so the description is the only source — yet it never explains what 'id' identifies or how 'offset' paginates. '50 at a time' only indirectly hints at offset semantics, leaving the required id parameter undocumented.

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 (Read) and resource (private responses to your form), which cleanly distinguishes it from forms_read/forms_list/forms_write that operate on the form itself. The scope (a given form's submissions) is clear, though no sibling is named explicitly.

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 word 'responses' — the agent can infer this is the tool for fetching submissions rather than the form definition — but there is no explicit when-to-use/when-not guidance and no pointer to forms_list or forms_read as alternatives.

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