list_prefs

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

The annotations already declare readOnlyHint: true, idempotentHint: true, and destructiveHint: false, so the description carries little behavioral burden here. It adds only the 'Get all' scope and the HTTP method, which is consistent with annotations but does not say the kind of preferences or any response behavior like pagination or formatting. No contradiction with any annotation is present.

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 two short lines with no filler. The intent is front-loaded, and the endpoint line adds minimal but useful context; there is no wasted text, which is appropriate for a parameterless read-only endpoint.

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 zero-parameter read-only endpoint with a rich output schema present, the description covers the important basics. The main weakness is ambiguity about whether 'preferences' refers to server-wide preferences or another scope, but the top-level end of 'GET /:/prefs' plus 'all' conveys the broad scope reasonably well.

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 is empty, so the description has no parameters to clarify; the no-parameter baseline of 4 applies. 'Get all preferences' and the endpoint pattern match this expected zero-parameter call.

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 'Get all preferences' supplies a clear verb and resource, and the GET /:/prefs endpoint confirms the read scope. It lacks an explicit differentiator within the large sibling set, since many other tools also deal with preferences (e.g., list_library_sections_prefs, get_library_sections_by_section_id_prefs, and a similarly-named list_prefs_get). Still, it communicates what the tool does accurately and distinctly enough for simple cases.

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?

There is no guidance on when to call this tool compared with the numerous other prefs-related siblings, nor any exclusion or fallback recommendation. The only implicit context is the root-level endpoint, which the agent must infer from the path alone. As a result, an agent could easily pick a different prefs tool for the same request.

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