mma_search

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

With no annotations, the description adds key behavioral info: cursor-based pagination, semantic ranking for 'q', and optional geo radius. It doesn't cover rate limits or side effects, but the added context is valuable.

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?

Two sentences efficiently convey purpose, key parameters, pagination pattern, and prerequisite. No redundant or unnecessary information.

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?

Given 6 parameters, no output schema, and no annotations, the description covers pagination and a prerequisite call. However, it mentions 'geo radius' which is not in the schema, and doesn't describe return format or error handling, leaving some gaps.

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?

Despite 50% schema coverage, the description explains the high-level meaning of parameters: category as slug, filters as structured facet filters, 'q' as semantic ranking. It compensates by giving the overall structure, though individual parameter details are left to the schema.

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 the tool's function as a structured marketplace search with category, facet filters, optional natural-language query, and optional geo radius. It distinguishes from sibling tools like mma_describe_catalog by positioning it as the search entry point.

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?

Provides explicit guidance to call mma_describe_catalog first to ensure filters use real facet keys. Also explains cursor pagination pattern (pass cursor until null), giving clear usage context.

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