List campaigns for a Video Ads channel

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the '[READ]' prefix is redundant. The description discloses nothing beyond that: no pagination, no result size, no auth or rate-limit notes. With annotations doing the safety work, the description contributes almost no additional behavioral context.

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?

Extremely short and front-loaded, which is good, but the '[READ] OpenAPI: GET ...' framing is boilerplate that duplicates annotations and consumes the entire body without informing the 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?

For a list tool with no output schema, the description should at minimum convey what is returned and whether results are paginated. Neither is present, and the single undocumented parameter is left unclarified, so the definition is thin even for a simple endpoint.

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?

There is one required parameter (channel_id) with 0% schema description coverage. The description's path template '{channel}' hints that this is the channel identifier, partially compensating for the missing schema description, but adds no format, ID type, or lookup guidance.

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 title 'List campaigns for a Video Ads channel' plus the path GET /channels/{channel}/campaigns conveys a list operation on campaigns scoped to a channel. But the description body itself only restates the HTTP verb and path, adding little beyond the title, and does not distinguish it from siblings like get_vads_campaign or list_vads_channels.

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?

There is no guidance on when to use this versus get_vads_campaign (single campaign) or list_vads_channels (parent list). The agent must infer usage entirely from the name and path, with no stated prerequisites or exclusions.

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