get_user_lists

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

No annotations are present, so the description carries full burden. It only states 'get', implying read-only, but provides no details about pagination, authentication, or other behavioral aspects. The description adds minimal value beyond the tool name.

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, front-loading the core action. However, it sacrifices necessary detail for brevity, which may hamper usability.

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 complexity (5 parameters, 2 enums, no output schema, no annotations), the description fails to provide sufficient context. It does not explain what a 'list' is, how pagination works, or what the response looks like, making it incomplete for effective use.

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?

With 0% schema description coverage and no parameter explanations in the description, the agent gains no additional meaning. The description does not clarify the purpose of parameters like 'page', 'per_page', 'sort', or 'sort_order', nor the expected format for 'username'.

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 'Get a user's lists' is a generic verb+resource, but it fails to specify what 'lists' refers to (e.g., wantlist, collection folders). Given siblings like get_user_wantlist and get_user_collection_folders, the description does not distinguish this tool's purpose from similar ones.

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. The description lacks context for when it is appropriate compared to sibling tools like get_user_wantlist or get_user_collection_items.

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