qdrant_points_scroll

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

Annotations already cover safety characteristics such as readOnlyHint, idempotentHint, and destructiveHint=false. The description adds the key behavioral contract around pagination, including the meaning of `next_page_offset` and the null termination condition, which goes beyond the annotations.

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?

The description is compact and front-loaded: purpose, pagination rule, then a concrete example. There is no filler, and the example earns its place by showing a minimal valid invocation.

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 6-parameter tool with a rich filter schema, the description covers the core scrolling mechanism and optional filtering, and an output schema exists to clarify return values. Still, it omits guidance on payload/vector inclusion parameters and does not address ordering or scan behavior, leaving noticeable gaps.

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 0%, so the description needed to compensate. It partially does by explaining `offset`, showing `collection_name` and `limit` in an example, and noting the `scroll_filter` via 'optionally filtered.' However, `with_payload`, `with_vectors`, and the full filter construction are left undocumented by the description.

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 action and resource: 'Page through all points in a collection, optionally filtered.' This clearly distinguishes the tool from sibling operations like point lookup, counting, or vector search, since it emphasizes bulk scanning and pagination.

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?

The description provides a clear pagination loop: pass the returned `next_page_offset` as `offset`, and treat `null` as the end of pages. This implies when the tool should be used, but it does not explicitly name alternatives or state when not to use, e.g., versus `qdrant_points_get` or `qdrant_query`.

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