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 two useful traits: it returns 'protection without secrets' (implying sensitive data is not exposed) and the revision required for subsequent changes. These go beyond structured data. It's cryptic but not contradictory.

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 brief (one list), but it's under-specified rather than concise: it's a fragment that omits the verb and reads like telegraphic notes. It doesn't front-load a clear statement of what the tool does.

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 one-parameter read-only getter with no output schema, the description should clearly state what it returns and how to use it. It lists some return categories but leaves catalogue_id semantics unexplained and the 'revision' mechanism vague. The description feels incomplete.

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% and the description never mentions catalogue_id, its format, or its semantics. The schema only gives name/type/pattern. The description does nothing to help an agent construct the parameter correctly.

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 states 'Read every reader and catalogue setting' and the description lists setting categories, so the verb+resource is identifiable. However, the description is a fragment rather than a sentence, and 'every reader' is ambiguous; it doesn't clearly differentiate itself from other getter tools like foliade_catalogue_status or foliade_get_shelf.

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 explicit when-to-use or when-not-to-use. The 'revision needed for changes' hints that this should be called before mutations, but the description doesn't name alternatives or conditions. An agent has to infer the tool's role in a workflow.

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