Popular Sharelists

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

Annotations already declare readOnlyHint and idempotentHint. Description adds value by specifying return fields (id, name, description, symbol_count, follower_count, creator) and sorting by popularity, which helps agents understand behavior beyond basic read-only nature.

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?

Single sentence with clear verb ('Get'), resource ('popular/trending community sharelists'), and output details. No unnecessary words; front-loaded with key information.

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?

Specifies return fields and sorting, which compensates for lack of output schema. However, does not mention pagination or behavior when count is 0, leaving minor gaps for a simple list tool.

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?

Only one parameter (count) with full schema explanation. Description does not add additional meaning beyond schema's existing description of count as number of lists to return with default of 20.

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?

Clearly states the tool retrieves popular/trending community sharelists with specific output fields and sorting by popularity. Distinguishes from sibling sharelist tools (e.g., sharelist_list, sharelist_detail) by specifying trending nature.

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 explicit guidance on when to use this tool versus alternatives like sharelist_list or sharelist_detail. Lacks context for when to prefer popular sharelists over other list retrieval methods.

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