list_yek_collections

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

With no annotations present, the description carries the full burden of disclosing behavior. It only states that the tool 'lists' facets, implying a read-only operation, but does not elaborate on side effects, permissions, or return characteristics. The description adds minimal behavioral context beyond the verb itself.

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 with no fluff, making it efficient to read. However, the brevity borders on under-specification, especially regarding the library parameter. It earns a 4 because it is well-structured and to the point, though a bit more detail would be beneficial.

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 tool's simplicity (one optional parameter, no annotations), the description is incomplete. It does not explain the role of the 'library' parameter, nor does it provide any context about the output beyond what an output schema might contain. The lack of parameter semantics and usage guidance leaves significant gaps for the agent.

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 input schema has one parameter, 'library', with zero description coverage (0%). The tool description fails to mention this parameter or explain how it affects the results. This leaves the agent completely in the dark about whether the library is a filter, an input, or something else.

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') and resource ('collection facets'), clearly distinguishing this tool from siblings like list_yek_libraries (lists libraries) and search_yek_works (searches works). The phrase 'published by the portal' adds context about the data source, making the purpose unambiguous.

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 provides no information about when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. Sibling tool names give some implicit context, but the description itself offers no guidance on selection.

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