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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds the concrete return envelope { count, next_skip, items } and the pagination contract, which is real behavioral information the agent needs. It omits auth requirements and rate limits, and the GET endpoint line is context rather than behavior.

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?

Four tight sentences: the resource, the return shape, the paging rule, the single-record mode, and the filtering options, all front-loaded. Nothing is redundant or padded.

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 7 optional parameters, no output schema, and 100% schema coverage, the description supplies the missing return shape and paging workflow, which is what an agent most needs. Only the absence of any cue about how this relates to plutio_list_forms keeps it from being fully 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 coverage is 100%, so every parameter including id, skip, sort, limit, query, formId, and filters is already well documented with examples. The description reinforces the two most decision-relevant paths (id for a single record, query/filters for narrowing) but adds no syntax or constraints beyond what the schema states.

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 names a specific resource and operation: 'Submitted responses to forms,' with a single-record mode noted via 'Pass id to read one record.' It is distinguishable from the sibling plutio_list_forms by naming responses rather than forms, though it never explicitly contrasts the two.

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?

It explains how to page ('pass next_skip as skip for the next page') and how to narrow results (exact-match fields vs. a MongoDB-style query), which covers operating modes. It says nothing about when this tool is preferable to plutio_list_forms or any other listing sibling, and there are no exclusions.

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