marketplace_search

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

With no annotations, the description carries the burden of disclosing behavior. It does mention key features (fuzzy matching, optional semantic search, filters, pagination), but it does not explain return format, sorting behavior, or whether semantic search has additional costs. As a read-only search tool, it omits some useful context but remains non-deceptive.

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 a single, front-loaded sentence that efficiently communicates the tool's core purpose and key features. No redundant words or filler.

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 tool has 9 parameters, no output schema, and no annotations. The description covers the basic search capability but does not explain what the response contains (e.g., list of matching tools with scores), nor does it clarify the difference between full-text and semantic search. This leaves the agent with unanswered questions for effective invocation.

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 coverage is 100%, so the baseline is 3. The description adds generic 'filters' and 'pagination' but does not map them to specific parameters. It also mentions 'fuzzy matching' which is not represented in the schema, potentially confusing. Overall, it adds little beyond 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 uses a specific verb ('Search') and resource ('tool marketplace'), clearly distinguishing it from sibling tools like marketplace_discover_tools or marketplace_get_tool. It also adds unique functionality (full-text, semantic search, fuzzy matching) that sets it apart.

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?

The description clearly implies this tool is for searching the marketplace. However, it does not explicitly mention alternatives or exclusions, such as when to use marketplace_discover_tools instead. The context is clear but lacks formal when/when-not guidance.

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