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 'Read-only' in the description merely repeats structured data. The description does add that results are paginated ('one page'), but gives no information on total counts, ordering, or what happens when kind/board_id mismatch.

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 front-loaded sentence that packs purpose, scope, filters, and a read-only note without padding. The colloquial 'picker' phrasing costs a little precision but the sentence is otherwise dense and waste-free.

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?

With 7 parameters, 14% schema coverage, no output schema, and a required 'kind' whose accepted values are never stated, the description is not complete enough for an agent to invoke this confidently. Key gaps (valid kind values, pagination limits/behavior) are unaddressed.

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 only 14% (just board_id), so the description must compensate but largely does not. It loosely maps 'search text, tags or category' to query/tag_ids/categories, but the required 'kind' parameter has no enum, no description, and no explanation of valid values, and page/page_size semantics are left entirely to the schema defaults.

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 states a specific verb+resource: it returns 'one page of the user's library items of one kind,' with filtering by search text, tags, or category. This distinguishes it as a paginated, filtered library listing. However, it does not name or contrast against the many sibling list_* and search_uwear_library tools, and the central discriminator ('kind') is never explained.

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 automation builder's picker' implies the usage context (during automation building) and the filter dimensions imply when each filter applies. But there is no explicit when-to-use vs. when-not, and no pointer to alternative tools like search_uwear_library or the sibling list_* tools. Usage is only implied.

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