kadam_adv_list_campaigns

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

Annotations already declare readOnlyHint=true, consistent with listing. The description adds pagination and filtering behavior, but does not complicate or contradict. No destructive behavior disclosed, which matches annotations.

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?

Single sentence, front-loaded with primary action and filter options. No redundancy or unnecessary text.

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?

No output schema is provided. The description does not explain the return format (e.g., what fields are in each campaign object, pagination metadata). While it's a list tool, an agent might need to know the response structure. Completeness is adequate but not fully comprehensive.

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 40% (4/10 parameters described in schema). The description names filter categories but does not detail parameter formats or constraints beyond what schema provides. For example, enum values for status/type are not mentioned. It adds marginal context but does not fully compensate for low coverage.

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 'List advertiser campaigns with pagination' and enumerates filtering options (folderId, status, type, date range, search query), distinguishing it from sibling tools like get_campaign (single) or create_campaign.

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 when to use (when you need a paginated, filtered list) but does not explicitly contrast with sibling tools like get_campaign for a single campaign or list_campaign_folders for folders. Still, the filtering context is clear.

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