get_user_lists

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds that only public lists are returned and that username defaults to the caller, which is useful context, but it omits auth requirements, rate limits, and pagination behavior.

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 front-loaded fragment with no filler, which is efficient. However, for a tool with three parameters and no schema descriptions, it is arguably too sparse to be appropriately sized.

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?

For a read-only list-retrieval tool with three parameters and no output schema, the description omits crucial context: what 'lists' are, how pagination works, and how this differs from sibling list/collection tools. Annotations cover safety but not domain specifics.

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 0%, so the description must compensate. It only clarifies the username default ('defaults to you'); page and per_page remain entirely undocumented in both schema and description.

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 names the resource ('A user's public lists') but provides no verb and largely restates the tool name with minor additions ('public', 'defaults to you'). It does not distinguish this tool from siblings like get_list or get_wantlist.

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 contains no when-to-use guidance, alternatives, or exclusions. 'Defaults to you' is a default parameter behavior, not usage guidance for selecting this tool over others.

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