getSmartList

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

The description declares read-only behavior (matching annotations) and adds return format details: '{ status: "success", message: [{...record}] }' and handling of not-found cases (empty or 404). This supplements the annotations with concrete response behavior.

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 compact and well-structured, using markdown for readability. Each sentence serves a distinct purpose: what, when, required param, see also, and return format. No unnecessary words.

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 fetch tool with one parameter, the description covers all essential aspects: operation type, usage context, required parameter, related tool, and return behavior (including error cases). No gaps remain.

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 description mentions that smart_list_id is required, but the schema already marks it required. With 0% schema description coverage, the description adds minimal value; however, the parameter name is self-explanatory given the tool's purpose, so a baseline score of 3 is appropriate.

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 'Get a single smart list - Fetch a single smartlist record. Read-only.' This specifies the verb (Get/Fetch) and the resource (smart list), distinguishing it from sibling tools like listSmartLists and other CRUD 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 explicitly provides a use case: 'Use when: fetching one saved filter's config.' It also references the sibling tool listSmartLists for enumeration, guiding when to choose this tool over alternatives.

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