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

The annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral context: results are grouped by folder, document_id is included, folder matching is partial, and limit is capped at 200. It does not disclose ordering or exact response shape, but annotations lower the burden.

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 three sentences, front-loaded with the core action, and every sentence adds useful detail. There is no redundant or filler text.

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 four-parameter list tool with no output schema, the description is largely complete: it covers listing behavior, folder filtering, pagination, and document_id inclusion. It leaves minor gaps around world_id semantics and result ordering, but annotations cover the safety profile.

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 must compensate for four parameters. It explains folder as a partial-match filter and offset/limit as paging with a maximum of 200, but it does not explicitly describe the required world_id parameter beyond the phrase 'a world's Lore Library'.

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: list documents in a world's Lore Library. It also states that results are grouped by folder and include document_id, making the operation clear. However, it does not explicitly distinguish this from siblings like search_lore or read_lore.

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 usage by explaining folder filtering and pagination, but it does not say when to use list_lore instead of search_lore or read_lore. There are no explicit exclusions or alternative-selection guidance.

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