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

Annotations already declare readOnly/openWorld/non-destructive, so the description only needs to add operating detail — which it does by disclosing the return envelope ({ count, next_skip, items }), the pagination handoff, and the underlying GET /forms call. No auth, rate-limit, or scope caveats are mentioned, keeping it short of a 5.

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?

Five short clauses, front-loaded with the resource and fields, then return shape, then paging, then filtering. 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 six optional parameters, no output schema, and nested filter objects, the description supplies exactly the missing pieces: the response envelope, how to page with next_skip, and the two filtering modes. An agent can invoke it correctly from this text plus the schema.

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% and every parameter is already documented (id, skip, sort, limit, query, filters). The description restates the skip/next_skip relationship and the id read behavior but adds no syntax or edge-case meaning 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?

States the resource concretely ('Forms (intake forms, questionnaires)') and what fields come back ('name and status'), which is enough to separate it from plutio_list_form_responses without opening either schema.

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 gives operational guidance ('Pass id to read one record', 'Filter with exact-match fields or a MongoDB-style query') but never says when to use this over sibling list tools or what the filter paths exclude. Usage is implied through mechanics rather than stated as selection criteria.

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