androidapi_get_wa_sent

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

The annotation readOnlyHint already marks it as read-only; the description adds the pagination behavior, which is key for understanding how to handle potentially large result sets.

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 one short sentence that immediately conveys the core functionality. No wasted words.

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, the description should describe the return structure. It does not, leaving the agent uninformed about the response format. Parameter descriptions are also lacking.

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?

With 0% schema description coverage, the description adds 'paginated' which hints at the purpose of page and limit, but fails to explain their meanings, defaults, or ranges.

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 tool lists 'sent WhatsApp chats' and notes pagination. It distinguishes from siblings like androidapi_get_wa_received and androidapi_get_wa_pending.

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?

Usage is implied by the description (to list sent WhatsApp chats), but no explicit guidance on when to use this tool versus alternatives is provided.

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