whatsapp_sync

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

With no annotations, the description carries the burden. It discloses that the tool forces a sync and blocks until completion ('THEN returns'). However, it does not mention potential side effects like overwriting local data, failure behavior, or whether it's idempotent. This partial transparency aligns with a mid-range score.

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 a single, well-structured sentence. It conveys the action, target, and synchronous nature without extraneous detail. The front-loaded verb 'Forces' and the added 'THEN returns' provide clarity in an extremely concise format.

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 the simplicity (no params, no output schema), the description covers the core behavior. However, it omits the return value (what the caller receives) and any failure/error semantics. It also doesn't explain that this is a prerequisite for reading fresh WhatsApp data, which would enhance usefulness.

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?

The tool has zero parameters and an empty schema, so schema coverage is 100%. Per the baseline for 0 params, a score of 4 is appropriate. The description doesn't need to elaborate on parameters that don't exist.

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 performs a sync: 'Forces WhatsApp to pull the latest messages, groups and contacts into the local store'. The verb 'pull' and the specific resources distinguish it from siblings like whatsapp_connect (connection setup) or whatsapp_list_chats (reading from local store).

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 is provided on when to invoke this tool versus alternatives. It doesn't mention that this should be called before reading latest data or that it's unnecessary when cached data is acceptable. The description is purely functional without contextual direction.

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