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 small behavioral clues by mentioning 'catalogues in order' (ordered output) and 'revision of the shelf' (returned version data), but it does not describe auth needs, not-found behavior, or any side effects beyond what the annotations convey.

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 very short and not wordy, but it is a fragment that lacks a verb and reads like a list of returned fields. It is concise in length, but the structure does not front-load the action or make the tool's behavior instantly graspable.

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 read-only get-by-id tool with annotations covering safety, the description gives some indication of return content (settings, catalogues in order, revision). However, with no output schema and no explicit statement of what a shelf is or what the response structure looks like, the definition is only minimally complete for an agent to invoke it correctly.

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?

There is one parameter, shelf_id, and schema description coverage is 0%. The description never mentions shelf_id or explains how to identify the shelf, so it adds no semantic value beyond the schema's field name and pattern.

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 title 'Read a shelf and its contents' supplies a specific verb and resource, and the name foliade_get_shelf aligns with this read operation, distinguishing it from list/create/update shelf siblings. However, the description body is an awkward noun phrase ('Settings, catalogues in order, and revision of the shelf') rather than a clear action statement, so it does not fully clarify purpose on its own.

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?

No guidance is provided on when to use this tool versus alternatives like foliade_list_shelves for listing shelves or foliade_update_shelf for modifying one. The read-only intent is implied by the name/title/annotations, but the description gives no explicit context, prerequisites, or exclusions.

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