send_sync_request

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

Discloses asynchronous nature ('data arrives in the background over the next few seconds') and explains architecture reason. No annotations provided, so description carries the burden. Could mention if any authorization required, but overall clear.

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?

Three sentences, front-loaded with purpose, then usage guidance, then behavioral note. No unnecessary 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 parameters, no output schema, and no annotations, the description fully covers purpose, when to use, async behavior, and exclusion. Complete for this simple tool.

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?

Input schema has no parameters. Baseline is 4. Description adds meaning by explaining what the sync entails, compensating for lack of params.

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?

Clearly states the tool requests a full sync of messages, contacts, and groups from the primary device. Specifies verb (request), resource (sync), and scope (messages, contacts, groups). Distinguishes from sibling tools like receive_messages.

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?

Explicitly tells when to use: when list_conversations shows no history, list_contacts returns fewer contacts, or list_groups is missing groups. Also tells when not to use: for new incoming messages, use receive_messages instead.

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