catalog_list

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

No annotations are provided, so the description carries the full disclosure burden, and it says nothing about whether the catalog is static metadata or computed at runtime, whether it requires any setup, or how large the response is. 'Merged' hints that entries are consolidated from multiple sources but this is never explained.

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 front-loaded sentence with the verb and scope first, followed by concrete counts that let an agent judge whether a follow-up tool is needed. The inventory detail is dense but earns its place as a preview of contents.

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 zero-parameter listing tool this is nearly adequate, but with no output schema the description never says what the returned entries look like (names, identifiers, categories) or whether those identifiers are usable as inputs to sibling tools. That is a meaningful gap for a discovery/index tool.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond what the empty schema already conveys. Baseline 4 applies.

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 verb 'Lists' plus the resource 'merged PixelForge capabilities' is specific, and the enumeration of the five capability families tells an agent exactly what the catalog covers. It doesn't explicitly differentiate itself from siblings like palette_tool or studio_info, which also surface overlapping information.

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?

There is no statement of when to call this versus alternatives such as palette_tool (palettes) or studio_info (studio metadata), nor any note on whether it should be called before other tools as a discovery step. The usage is only inferable from the content list.

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