search_asset

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

With no annotations provided, the description carries the burden of behavioral disclosure. It states that the tool uses 'official authenticated APIs,' implying network access and authentication requirements, and 'Searches' indicates a read-only operation. It does not cover rate limits or auth configuration, but for a low-risk search tool this is reasonably transparent.

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 sentence with no filler. The main action and marketplace scope are front-loaded, and the mention of official authenticated APIs is concise and useful.

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 search scope and parameters are clear, but because there is no output schema and no annotations, the description should say more about what the tool returns and any auth or error behavior. It is adequate for a simple search tool but leaves return-format details unstated.

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 description coverage is 100%, so the schema already documents keyword, limit, and assetType. The description adds some context by listing marketplace asset categories, but it does not clarify keyword syntax, limit behavior, or allowed assetType values beyond what the schema provides.

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 identifies the action as searching the Roblox Creator Store / Marketplace and lists specific asset categories (models, audios, decals, plugins). The verb 'searches' plus the resource scope makes the tool's purpose unmistakable and distinguishes it from non-search sibling tools.

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 conveys clear context: this is for marketplace asset search using official APIs. However, it gives no explicit guidance about when to use this tool versus alternatives such as studio_search, insert_asset, or upload_image, and it does not state any exclusions.

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