list_mylists

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

The annotations already mark this as a read-only, idempotent operation. The description adds the 'authenticated user's' scope, which clarifies that results are limited to the current user's MyLists. However, it does not elaborate on pagination behavior, response contents, or any other behavioral nuances.

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 consisting of seven words. It is front-loaded with the action and resource, and every word contributes meaning without unnecessary detail.

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?

The tool is simple, but the description leaves some gaps. It does not mention that pagination is controlled by limit and start_index, nor does it clarify whether the response includes list metadata only or also parts. Given no output schema, the description could be more complete by hinting at what the return value contains, though the annotations help fill the safety profile.

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 input schema has three parameters (limit, account_id, start_index) with no descriptions, and the schema description coverage is 0%. The description does not explain any of these parameters, leaving the agent to infer their meaning from names only. It provides minimal additional semantic value beyond the schema fields.

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 a specific action ('List') and a specific resource ('the authenticated user's DigiKey MyLists'). It distinguishes itself from sibling tools like get_mylist (which likely fetches a single list) and create_mylist by focusing on listing all of the user's lists.

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. It does not mention any exclusions or reference sibling tools, such as using get_mylist for a single list or search_products for product searches. The usage context is only implied by the tool name and description.

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