listSmartLists

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

With no annotations provided, the description carries the full burden of disclosure. It usefully reveals the default scope behavior and the effect of `all: true`. However, it does not disclose pagination behavior, return format, or the relationship between `all` and the `fub2` parameter, leaving some behavioral ambiguity.

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 two sentences, front-loaded with the primary action, and contains no filler. Every word contributes to understanding the tool's purpose and behavior.

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 covers the core purpose and the main nuance (classic vs current UI). However, it omits the `fub2` parameter's relation to `all`, does not mention pagination or response structure (no output schema), and leaves some uncertainty about how the agent should interpret the parameters. More detail would make it fully self-sufficient.

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 100%, so the baseline is 3. The description adds value by clarifying that the default is classic-only and specifying the `all: true` flag, which is not explicitly stated in the schema. This goes beyond the parameter descriptions.

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 'List all smart lists', which is a specific verb and resource. It also distinguishes between classic and current FUB smart lists, adding scope. It does not explicitly name sibling alternatives like getSmartList, but the plural 'all' adequately differentiates from single-list operations.

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 clear context on default behavior (classic only) and how to expand to include current FUB smart lists using `all: true`. This guides the agent on when to pass the additional parameter. However, it does not explicitly mention when not to use this tool or name alternatives, so it lacks full exclusions.

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