adb_market_export

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

The description discloses the output format (JSON file) and content fields, but lacks details on side effects (e.g., whether it creates a local file or returns data) or permissions needed. Since no annotations are provided, the description carries the full burden but is somewhat vague.

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 sentences, front-loaded with the core action, and contains no superfluous words. It efficiently communicates purpose and output.

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 no output schema or annotations, the description adequately covers the tool's function and output structure. It could mention where the JSON file is produced (e.g., stdout or local file) but is otherwise sufficient.

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%, but the description adds value by summarizing the output and providing guidance on the version parameter (suggesting increment on update). This goes beyond what the schema alone conveys.

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 tool exports a local workflow with marketplace metadata for sharing, specifying the output as a JSON file with name, description, version, author, and tags. It distinguishes from sibling tools like adb_market_install and adb_workflow_list.

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 usage for marketplace submission but does not explicitly state when to use this tool versus alternatives or provide exclusions. No guidance on prerequisites or when not to use it is given.

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