list_publishers

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

With no annotations provided, the description must communicate behavioral traits on its own. It only says 'List all publishers,' giving no detail on whether archived publishers are included, pagination behavior, authentication requirements, or return format, leaving significant ambiguity.

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?

A single, direct sentence conveys the purpose without unnecessary words or repetition. Information is front-loaded and easy to scan.

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 list endpoint with two self-explanatory pagination parameters, the description is minimally sufficient. However, it does not clarify whether 'all' includes archived publishers, and there is no output schema or return-value description, leaving some gaps.

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 has 100% coverage with descriptions for limit and offset. The tool description adds no additional parameter context, so the baseline of 3 applies for schema-driven clarity.

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 operation ('List all publishers') and the resource scope ('in your AdButler account'). It differentiates from sibling tools like get_publisher and list_archived_publishers by emphasizing the complete collection.

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 retrieving all publishers but does not explicitly state when to choose this over alternatives such as get_publisher or list_archived_publishers. No exclusions or alternative tool references are provided.

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