list_interests

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

Annotations indicate readOnlyHint=true, and the description confirms it lists data. It adds behavioral context: returns 404 for invalid category_id and describes the return structure. No contradictions. Does not repeat annotation info verbatim but adds useful details.

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?

Concise but thorough: a summary sentence, usage guidance, error note, and clearly labeled Args and Returns sections. No unnecessary words or redundancy.

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 adequately describes the return format (JSON with total_items and interests array, each interest's fields). It provides context with sibling tools and error behavior. Minor omission: the 'account' parameter is not explained, but overall complete for intended use.

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 schema coverage at 0%, the description explains the purpose and source for list_id and category_id, and details count and offset parameters including defaults and pagination. Only the 'account' parameter is not explained, but the rest are well-covered, adding significant 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 clearly states it lists interest options within a category with subscriber counts. It distinguishes from associated tools like list_interest_categories and add_member/update_member, specifying that this tool's output is needed for setting member preferences.

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?

Explicit guidance: use after list_interest_categories to see individual options. It advises not to use for managing member preferences directly and notes that interest IDs are needed for add_member/update_member. Also describes error behavior for invalid category_id.

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