mcp-wacli

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the three-step process (connect, fetch, exit) which is helpful, but lacks critical details: it doesn't specify what 'sync' entails beyond fetching messages, doesn't mention authentication requirements, error handling, rate limits, or what happens to existing messages. For a tool with no annotations, this leaves significant behavioral gaps.

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 perfectly structured and concise. The first sentence states the core purpose, followed by a clear bullet-point list explaining each parameter. Every sentence earns its place with no wasted words. The information is front-loaded with the main purpose stated first.

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 3 parameters with 0% schema coverage and no annotations or output schema, the description does a good job explaining parameter semantics but falls short on overall completeness. It doesn't explain what 'sync' means operationally, what types of messages are fetched, how results are returned, or error conditions. For a tool with no structured metadata, the description should provide more behavioral 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?

The description provides clear semantic explanations for all three parameters beyond what the schema offers (which has 0% description coverage). It explains that 'refresh_contacts' refreshes contacts from session store, 'refresh_groups' refreshes joined groups live, and 'download_media' downloads media in the background during sync. This adds meaningful context that the schema's boolean types and titles don't provide.

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's purpose with specific verbs and resources: 'Sync messages once (connect, fetch new messages, then exit).' It distinguishes from siblings by specifying a one-time sync operation rather than continuous syncing or other message-related functions. The description explicitly mentions the three-step process: connect, fetch new messages, then exit.

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 context through 'once' and 'then exit,' suggesting this is for a single synchronization operation rather than ongoing syncing. However, it doesn't explicitly state when to use this tool versus alternatives like continuous sync tools or when not to use it. No specific alternatives are named among the sibling tools.

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