romm_favorite

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

Without annotations, the description carries the full burden. It explains the behavior (finds or creates collection, then adds/removes ROM) and parameter semantics, but could be more specific about error cases or side effects. Still, it is adequately transparent for a simple toggle operation.

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?

Four sentences, each serving a purpose: summary, background, parameter explanations. No wasted words, front-loaded with the main action. Highly concise and well-structured.

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 the tool's simplicity and presence of an output schema (not shown), the description covers the core behavior and parameters adequately. It does not mention the return value explicitly, but for a toggle action, the output is likely self-explanatory. Slightly lacking in completeness for potential errors.

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?

Although the schema has 0% description coverage, the description thoroughly explains both parameters: rom_id as the ROM's ID and favorite as a boolean with default true, clearly stating its effect. This adds significant meaning 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 clearly states the action ('Add or remove a ROM from your Favorites') and explains the concept of favorites as a special collection, distinguishing it from sibling tools like romm_add_to_collection.

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 explains that favorites are a special collection, implying this tool is for the favorites collection, but it does not provide explicit guidance on when to use this versus alternatives, nor any when-not-to-use conditions.

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