mma_describe_catalog

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

The description explains the behavior with and without the category parameter, including live counts and returned facet types and enum values. It warns against inventing values, which is helpful, though it does not explicitly mention side effects or permissions; as a read operation, that is implicit.

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 concise, using two sentences to convey all necessary information without redundancy. It is well-structured and easily scannable.

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?

The description fully explains the tool's role in the context of searching and listing, including its prerequisite nature and the rule against inventing facets. It is complete for an agent to know when and how to use it effectively.

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 sole parameter 'category' is well-described in both the schema and the main description, with examples and a clear explanation of its effect on the output. Schema coverage is 100% and the description adds functional meaning.

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 clearly states that the tool reads the self-describing facet schema, distinguishing it from search or listing operations. It explicitly says 'BEFORE searching or listing,' making its purpose unambiguous.

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?

It provides explicit when-to-use guidance ('BEFORE searching or listing') and instructs users to only use facet keys and values returned by the tool, preventing misuse. This effectively differentiates it from sibling tools like search and listing.

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