Get user lists

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and scope are covered structurally. The description adds valuable behavioral context by excluding imported lists and specifying public-only access for other users, though it does not mention pagination or return shape.

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?

Two sentences, front-loaded with the main operation and scope, followed by the exclusion and alternative. There is no redundant or filler text.

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 readOnly/openWorld annotations and no output schema, the description covers enough for an agent to call the tool correctly: scope, exclusions, and the alternative for imported lists. It omits some parameter detail and pagination behavior, but those gaps are modest for this simple list tool.

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 67%, with username and unified documented but sort only represented as an enum. The description adds context for username ('another user's public lists') but does not explain sort values or unified merging, leaving some parameter meaning to the schema.

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 states a specific verb and resource ('List ... lists') and clearly scopes it to MDBList-made lists, distinguishing it from imported lists. It also explicitly routes imported lists to browse_lists, making the tool's purpose unambiguous against siblings.

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?

It gives clear context for use: the authenticated user's MDBList-made lists or another user's public lists, with an explicit exclusion and alternative for imported lists. It does not cover all sibling relationships, such as when to prefer search_lists, but the core routing is clear.

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