publish-catalog

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

No annotations exist, so description carries full burden. It discloses key behaviors: runs decode-merchant, writes files, persists, serves, and explicitly states what it never does (deploys infrastructure, holds keys, transacts). Provides clear side-effect information.

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?

Description is front-loaded with the core action ('Publish your own catalog by reading yourself') and provides essential details in three sentences. Slightly verbose but efficient given complexity.

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 annotations or output schema, the description thoroughly explains the complete workflow, file outputs, and invariants (e.g., no infrastructure, no keys). Covers all necessary context for selection and invocation.

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?

Input schema covers 100% of parameters with descriptions. The tool description does not add additional meaning beyond schema context (e.g., 'the merchant's own product URLs'). Baseline score of 3 is appropriate.

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's purpose: publishing a catalog by reading merchant product URLs, running decode-merchant, collecting CleanReads, and writing output files. Differentiates from sibling 'get-catalog' (read-only) by specifying write and persist actions.

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 use when a merchant wants to publish their own catalog, but does not explicitly contrast with siblings like 'get-catalog' or provide when-not-to-use criteria. Usage context is clear but lacks explicit guidance.

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