Roblox Search Mechanics

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

No annotations are provided, so the description must disclose behavioral traits. It only states what the tool searches for, not any behavioral details such as read-only status, potential rate limits, authentication requirements, or how results are returned. This leaves the agent without crucial behavioral context.

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, focused sentence with no unnecessary words. It is front-loaded with the key information and is easy to parse quickly. Every word contributes to the purpose.

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 there is no output schema, the description could more fully describe what the search returns (e.g., item details, pagination). However, as a simple search tool, the current level of completeness is minimally adequate but could be improved to cover return value expectations.

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% for both parameters. The description does not add new semantic meaning beyond the schema; it merely provides example keywords. The schema already documents 'keyword' and 'limit' adequately, so no extra value is needed.

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 purpose: 'search specifically for gameplay mechanics, movement systems, physics controllers, and interactive scripts' in the Roblox Creator Store. It includes concrete examples (e.g. double jump, grappling hook) that help identify the category. This distinguishes it from sibling search tools focused on other asset types.

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 implicitly guides when to use the tool: when searching for mechanics. However, it does not explicitly mention alternatives or when not to use it. Given the many sibling search tools, more explicit guidance would be beneficial, but the phrase 'search specifically for' sets appropriate expectations.

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