list_items

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

No annotations are provided, so the description carries the full burden. It does disclose pagination support and JSON output, which is useful. However, it does not explicitly state that the operation is read-only, describe the response shape or cursor mechanics, or clarify default filtering behavior for trashed items.

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 action-first sentence with no filler. It is appropriately concise, though it could have used a second sentence to route the agent toward search_items or view_item for other item operations.

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 eight parameters, no output schema, and no annotations, a bit more high-level context would help. The schema documents the parameters well, but the description does not mention the exactly-one-of shareId/vaultName requirement, what happens with no scope, or the shape of the returned paginated response. It is adequate but has clear 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 100%, so the baseline is 3. All eight parameters have descriptions covering defaults, allowed enums, formats, and the shareId/vaultName mutual exclusion. The tool description itself adds no parameter meaning beyond what the schema already provides.

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 ('List'), resource ('items'), and scope ('a vault or share'), with a mention of pagination and JSON output. It does not explicitly contrast with sibling search_items or view_item, so it is clear but not sharply differentiated.

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?

Only general context is given: list items for a vault or share. There is no explicit guidance about when to choose list_items over search_items or view_item, nor are any exclusions stated. The intended usage has to be inferred from the tool name and basic description.

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