list_import_lists

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

With no annotations provided, the description carries the burden of behavioral disclosure. It notably reveals that secret field values are masked and that the 'fields' array is deliberately omitted, which is valuable non-obvious behavior. It does not detail return shape, but for a param-less list tool this is adequate.

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 compact sentences with no filler. The primary purpose is front-loaded, and the second sentence adds high-value behavioral detail and a pointer to the sibling tool. Every word earns its place.

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 no-parameter list operation, this description is complete. It tells the agent what the tool returns at a high level, warns about omitted fields and masked secrets, and routes to get_import_list for more detail. No critical information is missing given the tool's simplicity.

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 is empty, so there are no parameter semantics to clarify. Per the baseline for zero-parameter tools, this is appropriately handled; the description correctly avoids adding irrelevant parameter detail.

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 tool's action ('List') and resource ('configured import lists'). It also differentiates itself from get_import_list by explicitly noting that the 'fields' array is omitted here, making the scope and relationship to siblings clear.

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?

The description provides an explicit alternative: 'use get_import_list for it' when the full fields array is needed. This gives concrete when-not-to-use-this-tool guidance, though it could go slightly further by describing when the list endpoint is preferred over get_import_list.

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