adobe_catalog_libraries

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

The description usefully discloses what the status payload contains and that refresh reconnects plus rebuilds the catalog — behavior the annotations do not spell out. However, 'rebuilds the catalog' is a state-changing side effect on the server, which sits awkwardly against readOnlyHint=true and openWorldHint=false; the description neither acknowledges that tension nor says whether the refresh is destructive, persistent, or costly (rate/time).

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?

One front-loaded sentence gives the resource first and the parameter note second, with zero filler. Slightly dense parenthetical packing, but every clause carries information an agent needs.

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?

With no output schema, the description does a fair job of enumerating return content (installed/built, tool counts, setup notes), and the single parameter is covered. It remains incomplete on the one risky path — what refresh:true actually changes, how long it takes, and whether it can fail or invalidate other catalog state referenced by adobe_catalog_call.

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 carry the single parameter, and it does: it names refresh and explains both its effect (reconnect) and its outcome (rebuild the catalog), which is more than a boolean name conveys. Missing only details like default value and cost/duration of a rebuild.

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?

States the specific resource (bundled community MCP libraries) and exactly what is returned: installed/built state, tool counts, setup notes. That is far more concrete than the bare name, but it never distinguishes this from sibling catalog tools such as adobe_catalog_describe, adobe_catalog_search, or adobe_catalog_call, leaving an agent to infer the boundary.

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?

Usage is only implied by the word 'Status' and the parenthetical inventory list; there is no explicit 'use this when…' statement and no mention of the sibling catalog tools that could be confused with it. The one piece of real guidance is the refresh semantics, which is framed as a parameter note rather than a when-to-use rule.

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