qdrant-list-document-ids

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

The description adds 'with pagination support,' which is a behavioral trait beyond the schema, but with no annotations, it fails to state if the operation is read-only, any potential side effects, ordering, or limitations. The pagination hint is useful but minimal.

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 a single sentence of 5 words, very concise and front-loaded. However, it sacrifices some informative content for brevity.

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?

Given no output schema and no annotations, the description should explain return format, any ordering, or constraints. Only pagination is mentioned, leaving out what the tool actually returns (list of IDs) and other behavioral details important for an AI agent to invoke 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 100%, so baseline is 3. The description does not add any additional meaning beyond the schema's parameter descriptions; it only mentions pagination generically without linking to the limit/offset parameters.

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 clearly states 'List document IDs with pagination support,' indicating the verb and resource. However, it does not differentiate from sibling tools like 'qdrant-get-documents' or 'qdrant-scroll-points' which also list or retrieve documents.

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?

No guidance is provided on when to use this tool versus alternatives such as 'qdrant-get-documents' or 'qdrant-scroll-points'. There are no usage contexts, prerequisites, or exclusions mentioned.

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