List Items created in this session

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

With no annotations, the description carries the full burden of behavioral disclosure. It does state that no tokens are returned, which is helpful, but it omits that the tool only lists items created in the current session (a key limitation) and does not clarify that it is a read-only operation. The phrase 'the vault knows about' is ambiguous and could mislead an agent into thinking it lists all known items, when the title suggests session-only scope.

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, concise sentence that front-loads the action and includes the key behavioral note about tokens. There is no wasted wording, and it is appropriately brief for a zero-parameter tool.

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 simple list tool with no parameters and no output schema, the description is mostly sufficient. However, it does not clarify the session-specific scope or differentiate from plaid_item_get, which could lead to incorrect selection. Given the large set of sibling tools, a note on when to use this versus alternatives would improve completeness.

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?

The tool has zero parameters, and the schema coverage is trivially 100% (empty properties). Per the rubric, the baseline is 4. The description adds no parameter-specific information, but none is needed since no parameters exist.

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 the action ('Lists') and the resource ('item_ids'), and explicitly notes that tokens are not returned. This distinguishes it from tools that retrieve full item details or tokens, such as plaid_item_get or plaid_auth_get, making the purpose unambiguous.

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 given on when to use this tool versus the many sibling tools. It does not mention that this is specifically for items created in the current session, nor does it contrast with plaid_item_get or other item-related tools. The title hints at session scope, but the description does not reinforce it, leaving the agent without clear selection criteria.

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