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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavior beyond that: results are paginated, and passwords are deliberately omitted from the response. No contradiction with annotations.

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, tightly written sentence that front-loads the core purpose ('Paginated list of the shelves and their settings') and appends the important redaction detail ('without passwords'). No wasted words.

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 low-complexity, read-only list operation with annotations covering safety, the description is mostly sufficient. It states pagination, content scope, and sensitive-data exclusion. However, with no output schema, it could briefly note what kinds of settings are returned or how pagination behaves, though this is not a critical gap.

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 carries some burden. 'Paginated' implies that limit and offset control result chunking, which adds minimal meaning beyond the self-explanatory parameter names and schema constraints. However, it does not clarify defaults, maximums, or the effect of each parameter beyond what the schema already states.

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 and resource: 'Paginated list of the shelves and their settings.' It clearly identifies the object category (shelves) and distinguishes itself from sibling list tools like foliade_list_catalogues, foliade_list_themes, and foliade_list_tracking_links. The qualifier 'without passwords' adds a useful scope clarification.

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 implies a listing use case but gives no explicit guidance on when to choose this tool over foliade_get_shelf (single shelf retrieval) or how it relates to shelf creation/updating tools. Sibling alternatives exist, but no conditions or exclusions are stated.

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