createSmartList

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

Annotations are minimal (readOnlyHint=false, destructiveHint=false). The description adds significant behavioral context: it writes live data, warns about duplicate name confusion, explains backend encryption behavior ('do NOT pre-encrypt'), and notes that the format of smart_list_query_params depends on smart_list_type. This goes well beyond the annotations.

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 front-loaded with the core purpose and flows logically through use case, requirements, pre-check, parameter details, and cross-reference. However, it is verbose—the pre-check block contains multi-sentence instructions that could be condensed without losing value. Slightly over-communicates.

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 tool with 5 parameters, no output schema, and lightweight annotations, the description covers everything an agent needs: purpose, required fields, parameter interactions, duplicate handling, and an alternative tool. It is fully self-contained and leaves no obvious gaps.

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?

Input schema covers 3 of 5 parameters (60%) but descriptions are sparse. The description extensively explains the conditional format of smart_list_query_params based on smart_list_type, the 'NA' sentinel for no filters, and the encryption warning. It also identifies smart_list_created_by as an admin user ID. This adds critical meaning beyond the schema.

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 starts with a clear verb+resource: 'Create a smart list - Create a new smartlist record. Writes live data.' It distinguishes from sibling tools like updateSmartList by explaining the creation context and noting alternative uses. The purpose is unmistakable.

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 explicitly states 'Use when: programmatically saving a filter configuration for later reuse.' It provides a detailed pre-check for name uniqueness and instructs what to do if a duplicate exists, including rerouting to updateSmartList. This provides clear when-to-use and when-not-to-use guidance.

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