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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's only added behavioral detail is the newest-first ordering; it says nothing about pagination semantics or volume, which the schema partly covers.

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?

A single short sentence with the resource and ordering constraint front-loaded and no filler. Brevity is appropriate for a trivial list tool, though it verges on under-specified rather than maximally efficient.

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 simple, fully annotated read with a 100%-covered two-param schema, the description is adequate but thin: it omits the relationship to search/read siblings and the double-mode pagination caveat that lives only in the schema.

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 coverage is 100% and both parameters carry rich descriptions, including the notable legacy bare-array vs { items, next_cursor, limit } behavior. The description adds no parameter information beyond the schema, so the baseline 3 applies.

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_setting rows) and adds a useful ordering detail ('newest first'). It doesn't explicitly distinguish itself from the sibling user_setting_search or user_setting_read, but the naming makes the retrieval-vs-filtering split reasonably inferable.

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?

Usage is only implied by the verb 'list'; there's no statement about when to prefer this over user_setting_search (filtering) or user_setting_read (single row). The agent must infer the paging/enumeration context on its own.

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