list_interests

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

Despite no annotations, the description fully covers behavioral traits: authentication via API key, max 10 concurrent requests, read-only and safe to retry, and 404 error for invalid category_id. All necessary for safe invocation.

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?

Well-structured into paragraphs with front-loaded purpose, but slightly verbose. Could merge some sentences without loss. Still efficient and clearly organized.

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?

Given the output schema exists, the description adds necessary context: auth, rate limiting, error, parameter details, and return format. Covers all aspects needed for correct tool usage.

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?

With 0% schema description coverage, the description compensates by explaining each parameter: list_id (source and format), category_id (source), count (default and range), offset (pagination use). Adds meaning far 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 clearly states 'List interest options within a category, with subscriber counts per option.' It uses a specific verb and resource, and differentiates from siblings like list_interest_categories and list_audiences.

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?

Explicitly says to use after list_interest_categories, explains that interest IDs are needed for add_member/update_member, and warns against using to manage preferences directly. Provides clear context and alternatives.

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