adb_market_search

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

No annotations are provided, so the description partially carries the burden. It describes that the tool shows information and indicates installed status, but does not explicitly state that it is read-only or non-destructive. Since it is a search, side effects are unlikely, but the description could be more explicit.

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?

Two sentences that are front-loaded with the purpose and efficiently describe the tool's functionality and output. No extraneous words or repetition.

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?

For a simple search tool with two optional parameters and no output schema, the description covers the main functionality, output details (name, description, tags, author, step count), and installed status. It is sufficient for an agent to understand and invoke the tool correctly, though pagination or sorting details are not mentioned.

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%, so the baseline is 3. The description adds context by explaining that 'query' filters by name, description, or tag keyword, and 'tag' filters by exact tag, which reinforces the schema but does not add significant new meaning beyond what the parameter descriptions already provide.

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 verb 'Search' and the resource 'workflow marketplace', and distinguishes from sibling tools like adb_market_install and adb_market_export by specifying it searches community-shared definitions. It also lists what information is shown, making the purpose unambiguous.

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 implies when to use (to search for workflows) but does not explicitly state when not to use or provide alternatives. No guidance is given on comparison with other search tools like adb_registry_search. Usage context is clear but exclusion criteria are missing.

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