get_lists

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It doesn't mention whether this is a read-only operation, whether pagination applies, what happens with the archived parameter default, or any rate-limit or auth considerations. A read tool with this many siblings should clarify its read-only nature.

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?

A single concise sentence with no wasted words. Efficient, though could not be considered overly terse since it accomplishes the basic purpose.

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 read operation with 100% schema coverage and no output schema, the one-line description is mostly adequate. However, given the presence of get_folderless_lists and get_list as siblings, some clarification on list scoping (folder-specific vs folderless) would improve completeness. The archived parameter behavior could also be clearer.

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 both parameters are documented in the schema. The description adds no param detail beyond what the schema already provides, so baseline 3 is appropriate. The archived parameter's default behavior is not clarified anywhere.

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?

Describes 'Get all lists in a folder' with a specific verb+resource+scope. Clear distinction from siblings like get_list (single), get_folderless_lists, and create_list. Slightly underspecified on return behavior but the core purpose is evident.

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 when/when-not guidance provided. The description doesn't explain when to use this versus get_folderless_lists, get_list, or get_tasks. An agent must infer context from the sibling names without explicit direction.

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