umbrella_list_destination_lists

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

With no annotations provided, the description carries the behavioral disclosure burden. It does state the operation is a list and defines the scope ('configured for this Umbrella organization'), but it does not mention pagination behavior, return format, or any access requirements. This is adequate for a simple read-only list operation but not rich in detail.

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, front-loaded sentence with no filler or redundancy. It states exactly what the tool does in as few words as possible.

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 description is sufficient for basic understanding, but there is no output schema and no mention of pagination semantics or how additionalParams affect the call. Since the tool is simple and the schema covers parameters, the gaps are not severe, but they prevent full contextual completeness.

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 already provides 100% coverage for limit, offset, and additionalParams, each with descriptions. The tool description adds no extra parameter-level meaning beyond the schema, so the baseline score of 3 applies.

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 uses a specific verb and resource: 'List all destination lists (allow/block lists) configured for this Umbrella organization.' It clearly identifies the object and scope, distinguishing it from the similarly named sibling 'umbrella_list_destinations' by referring to the lists themselves rather than the destinations within them.

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 intended use is implied: use this tool when you need to enumerate destination lists for the organization. However, there is no explicit comparison to alternatives such as umbrella_list_destinations or any guidance on when not to use this tool.

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