compare_colors

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

No annotations provided. Description states returns boolean but does not mention prerequisites (e.g., connected device), side effects, or whether it captures screen or uses existing data.

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?

Extremely concise: two simple sentences front-loading the action and purpose. No redundant words.

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 basic purpose and return type but lacks context on prerequisites, alternate tools, or detailed behavior. Adequate for the tool's simplicity but not fully complete.

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%. Description adds an example for 'colors' parameter, enhancing understanding beyond the schema. 'diff' parameter is well-described in schema. Overall, moderate added value.

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?

Description clearly states the tool compares colors at multiple screen positions, returns boolean, and is used for UI state determination. It distinguishes from siblings like 'find_colors' which likely searches for colors.

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?

Only a brief hint ('用于判断界面状态') about usage. No explicit when-to-use or when-not-to-use compared to alternatives like 'find_colors', 'ocr', or 'dump_ui_tree'.

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