marketplace_search

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

With no annotations, the description carries full burden and thoroughly explains synthetic bridge-side handler, HTTPS fetch, no auth, no API key, and CC0 asset licensing details, ensuring behavioral transparency.

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 verbose with extensive licensing details, which though valuable, could be condensed. It is well-structured but slightly wordy.

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?

Covers most aspects but lacks detail on the output structure ('normalised list') and how results integrate with marketplace_import. Adequate given no output schema.

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% (baseline 3). Description adds value by explaining search behavior (matches name/tags/categories), default behavior for empty query, and defaults for source, asset_type, and limit.

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 searches free CC0 asset marketplaces (Polyhaven, AmbientCG) for textures/HDRIs/models and returns a normalized list, distinguishing it from sibling marketplace_import.

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 context on when to use (searching CC0 assets), notes licensing distinctions, and suggests pairing with marketplace_import. Missing explicit exclusions but covers key usage scenarios.

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