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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds the sort order (newest first), which is genuine extra behavior. It does not mention the two different response shapes (legacy bare array vs { items, next_cursor, limit }), though that detail lives in the schema.

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?

One short sentence, front-loaded with verb and resource, with zero filler. It is perhaps over-terse for the pagination complexity involved, but nothing is wasted.

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?

Zero required params, no nesting, and a fully documented schema mean little context is strictly needed. Still, the description gives no hint of what a user_interest row represents or that two distinct response envelopes exist, which an agent would want before choosing limit/cursor.

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 description coverage is 100% and both limit and cursor are documented with their tricky legacy-mode interaction, so the schema does the heavy lifting. The description adds no parameter meaning beyond it, which is the baseline case.

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?

States a specific verb (List) and resource (user_interest rows) plus an ordering guarantee (newest first). It is distinguishable from its siblings user_interest_delete and user_interest_upsert by the verb alone, but the description never explicitly contrasts with them.

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?

No guidance on when to use this versus user_interest_upsert or user_interest_delete, and no stated preconditions. The agent must infer that this is the read path purely from the word "List".

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