androidapi_get_wa_campaigns

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is clear. The description adds the pagination behavior, which is useful. However, it does not disclose rate limits, sorting, or default page/limit values. With annotations covering core traits, a 3 is appropriate.

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: two words plus a parenthetical. It is front-loaded with the core action. While short, it saves tokens, but could be more helpful without adding significant length.

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?

Given no output schema and only two undocumented parameters, the description is incomplete. It does not explain response structure, pagination offset vs page number, or default behaviors. An agent would lack sufficient context to correctly interpret results.

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 0%, so the description must compensate. The term 'paginated' implies that page and limit are pagination parameters, but it does not specify that page may be 1-indexed or limit max values. This is insufficient for an agent to correctly set parameters without additional knowledge.

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 'List WhatsApp campaigns (paginated)' clearly identifies the action (list) and the resource (WhatsApp campaigns), and the pagination mention adds specificity. It distinguishes from siblings like androidapi_get_contacts or androidapi_get_groups, but not from other campaign list tools; however, the 'wa' prefix makes it clear.

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?

No guidance on when to use this tool vs alternatives. There is no mention of prerequisites, filters, or context that would help an agent decide to invoke it. The description is entirely declarative without usage instructions.

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