chromium_parse_favicons_tool

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

With no annotations provided, the description carries the full burden. 'Parse' implies a read-only operation, but the description does not explicitly state that the tool is non-destructive, nor does it mention any potential side effects or requirements like an accessible, unlocked database. It adds minimal behavioral context beyond the purpose.

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 two compact sentences. The first states the core purpose clearly, and the second provides a concrete example of the typical profile path, which is practical and directly helpful for an agent preparing an invocation. Every sentence earns its place with no redundancy.

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 description is adequate for a focused parse tool given the presence of an output schema and full parameter documentation. However, it lacks any contextual differentiation from the many sibling Chromium/Firefox parse tools and does not mention factors like database lock status or how the tool handles missing profiles. It meets the minimum viable bar but has clear gaps.

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?

The input schema has 100% parameter description coverage, so the schema already documents all six parameters in detail. The tool description adds no extra meaning to the parameters, such as how 'limit' interacts with filters or how 'include_image' affects output. Baseline 3 is appropriate given the high schema coverage.

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 uses a specific verb+resource: 'Parse Chromium favicons from the Favicons database.' This clearly distinguishes it from sibling tools like chromium_parse_history_tool and firefox_parse_favicons_tool by naming the exact data source and browser type.

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?

No guidance is provided on when to use this tool versus alternatives. It only states purpose and a typical profile path, with no mention of exclusions or alternative tools such as firefox_parse_favicons_tool for non-Chromium browsers. The usage context is implied solely by the tool's name.

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