printify_list_operations

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that the API is merchant-facing and that all operations are reachable with an ordinary token, adding meaningful auth/permission context. It could mention more about the output format, but the essentials are covered.

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 concise and front-loaded, with the main purpose in the first sentence and the usage guidance in the last. One of the sentences ('Printify's API is entirely merchant-facing...') is contextual but earns its place by clarifying reachability and token permissions.

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 listing tool with one optional parameter and no output schema, the description provides adequate context: what the tool does, how it relates to printify_call, and that all operations are accessible. It could be more explicit about what the returned entries look like, but the core calling scenario is well covered.

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 already provides 100% coverage with a clear description for the single optional 'search' parameter. The description adds general context about finding an operation id but does not need to re-explain parameter semantics. Baseline 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 states a specific verb ('Browse'), the resource (all 49 operations in the Printify API), and clearly explains its role as a discovery tool for finding operation ids to use with printify_call. This clearly distinguishes it from the sibling operation tools.

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 gives clear context that this is the intended tool for browsing available operations and specifically instructs the agent to use it to find an operation id for printify_call. It does not explicitly state when not to use it, but the use case is clear enough.

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