List Sharelists

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, which cover the safety profile. The description adds context about the list scope (own and subscribed) but does not disclose details like output structure or pagination behavior. Since annotations handle the main traits, a score of 3 is appropriate.

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 a single concise sentence that directly communicates the tool's function. There is no extraneous information or repetition.

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 simple nature of the tool, the existing annotations, and the presence of an output schema, the description adequately conveys the purpose and scope. It could mention that it returns an array of sharelists, but the output schema likely covers that. It is complete enough for agent invocation.

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 only parameter 'count' is fully described in the schema with its default and purpose. The description adds no additional meaning beyond what the schema provides. With 100% schema coverage, the baseline is 3, and the description does not exceed that.

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 uses a specific verb 'List' with a defined scope: 'user's own and subscribed community sharelists'. This clearly distinguishes from sibling tools like sharelist_popular, which lists popular sharelists, and sharelist_detail for single list details. The purpose is unambiguous and tailored.

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 indicates the function lists personal and subscribed sharelists, implying that for community-wide popular lists, one would use a different tool (e.g., sharelist_popular). However, it does not explicitly mention alternatives or provide explicit when-to-use guidance, but the scope definition itself gives clear context.

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