list_publishing_destinations

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

No annotations are provided, placing full burden on the description. The description only says 'available,' implying a read-only operation, but fails to disclose authentication needs, rate limits, or any side effects. Without annotations, a more thorough description is needed to cover behavioral traits.

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 extremely concise at one sentence with no wasted words. However, it lacks structure such as bullet points or sections. For a simple list tool, this is acceptable, but adding a brief usage note would improve it without sacrificing conciseness.

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 has an output schema (context signals indicate 'Has output schema: true'), so the description does not need to explain return values. Combined with full schema parameter descriptions, the description is adequate for a straightforward listing tool, though it could briefly define 'publishing destinations.'

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 description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond what the input schema provides for the three parameters (limit, start, filter_name). It does not elaborate on how these parameters affect the listing or provide context.

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 exactly what the tool does: 'List available publishing destinations.' It uses a specific verb ('List') and resource ('publishing destinations'), clearly distinguishing it from sibling tools which cover different actions (e.g., cancel_job, upload_data).

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 provides no guidance on when to use this tool versus its many siblings. It does not explain use cases, alternatives, or prerequisites, despite numerous sibling tools with overlapping or related functionality (e.g., list_reports, list_files).

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