list_catalogs

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the listing action and scope, omitting details like pagination behavior, return format, read-only nature, or any access requirements. For a simple list operation, this is acceptable but not transparent.

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 a single, front-loaded sentence that states the essential purpose without redundancy. Every word earns its place, and it is easily scannable for an agent.

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 tool is simple, the schema is complete, but there is no output schema and no behavioral notes. The description explains what the tool does but not what the response looks like or how pagination/fields are handled beyond schema hints. This is minimally viable for a list operation.

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 schema has 100% coverage with clear descriptions for all three parameters (after, limit, fields). The description adds no parameter-specific meaning, which is acceptable given thorough schema documentation. Baseline 3 applies because the schema does the heavy lifting.

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 ('List') and resource ('product catalogs') scoped to 'the ad account', clearly distinguishing it from sibling tools like get_catalog, create_catalog, and update_catalog. It is immediately obvious what action is performed on which entity.

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 context by specifying 'for the ad account', but it does not explicitly state when to choose this over alternatives such as get_catalog or list_product_sets. There are no exclusions or alternative tool mentions, so guidance is present but minimal.

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