See the stories people posted

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

Annotations already cover read-only/idempotent/open-world safety, and the description adds real substance on top: a 24-hour retention rule ('nothing older is held'), newest-first ordering, and how previews are produced (WhatsApp's preview when available, otherwise downloaded once and shrunk locally). It stops short of covering auth or per-call cost implications.

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?

Four sentences, front-loaded with scope and ordering before mechanics; nearly every clause carries information. Slight redundancy in 'WhatsApp keeps a story for a day and so does wazap' costs a point but not much.

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?

With no output schema, the description carries the return shape (author, text/caption, time, optional preview images) and the retention/ordering rules, which is everything an agent needs to invoke and interpret this read-only tool correctly.

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 coverage is 100%, which sets a baseline of 3, but the description adds meaning beyond the schema: previews arrive as 'small images', the retention ceiling explains why hours caps at 24, and it links message_id semantics to download_media. account_id receives no additional explanation, keeping it from a 5.

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?

States a specific verb and resource: the stories (status updates) the linked account has received in the last N hours, newest first, each with author, text/caption and time. It explicitly distinguishes itself from siblings by noting stories never appear in chats, catch-ups or waits, so an agent can route correctly without opening a schema.

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?

Gives a clear when-not for sibling tools ('Stories never appear in chats, catch-ups or waits; this is the only place they show') and points to download_media for retrieving a story's media via message_id. It lacks explicit guidance on choosing hours or when previews are worth requesting, but the routing context is strong.

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