unipile_get_recent_messages

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

With no annotations, the description carries full burden. It details return fields (text, sender, timestamps, attachments, etc.), but lacks disclosure on side effects, rate limits, idempotency, or reading permissions. The 'get' action implies read-only but is not stated.

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?

Two sentences with no superfluous text. First sentence states core action, second enumerates supported platforms and return details. Front-loaded and efficient.

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 tool with no output schema, the description explains return details adequately. However, it omits pagination behavior, ordering of messages, and does not mention the default batch size (schema covers it). Minor gap in complete context.

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 covers both parameters with descriptions (100% coverage), so baseline is 3. The description adds context about supported platforms but does not elaborate on parameter usage beyond schema. No new semantic value for parameters.

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 retrieves recent messages from all chats for a specific account, listing supported platforms. It distinguishes itself from sibling tools (unipile_get_accounts, unipile_get_emails) by focusing on messages across chat platforms.

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 usage for fetching recent messages but does not explicitly specify when to use versus alternatives or provide any exclusions. No guidance on prerequisite actions or when not to use.

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