romm_search

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

No annotations provided, so description must disclose behavioral traits. It only describes search behavior but omits side effects, rate limits, auth needs, or read-only nature. Unclear if tool is read-only or has other implications.

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?

Description is extremely concise: one sentence followed by parameter list. No fluff, front-loaded with main action. Every sentence earned its place.

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?

Tool has 3 parameters and no annotations; output schema exists but is not shown. Description covers basic parameter use but lacks output format, pagination, or error handling. Minimal but adequate for a simple search tool.

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 0%, so description carries full burden. It adds meaning: 'query' is a search term, 'platform_id' filters to a platform (0=all), 'limit' is max results (default 20). Adds basic value but not deep semantics.

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 'Search ROMs by name across the library,' specifying the action and resource. It distinguishes from sibling tools like romm_search_by_hash and romm_library_items.

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?

Description explains parameters (query, platform_id, limit) but does not explicitly state when to use this tool over alternatives like romm_search_by_hash or romm_library_items. No context on when-not-to-use.

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