list_item_members

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

There are no annotations, so the description carries the full burden of behavioral disclosure. 'List item members.' implies a read-only operation but does not state authentication needs, return format, pagination, or any side-effect guarantees. This is minimal, though not misleading.

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 extremely short, but brevity here is under-specification rather than successful conciseness. It is a single restatement of the name with no structure or additional detail, so it does not earn its place as helpful content.

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 the tool requires two parameters and is part of a family of member- and sharing-related tools, the description is incomplete. It does not clarify what 'item members' means in this context, what the output contains, or how this listing relates to similar operations like list_vault_members.

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 parameters (shareId, itemId, output) are already documented in the schema. The description adds nothing about parameters, but it also does not need to for the baseline, since the structured schema already explains what each parameter means.

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 'List item members.' is a direct restatement of the tool name (list_item_members) with spaces and punctuation, adding no new semantic information. It does identify a verb and resource, but because it is a tautology it fails the bar for even a clear-but-undifferentiated purpose.

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 about when to use this tool versus alternatives. Sibling tools like list_vault_members, update_item_member, remove_item_member, and share_item exist, but the description gives no context on how list_item_members fits among them.

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