weflow_sns_export_stats

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only implies a read operation via 'Get' but does not disclose side effects, required permissions, or the behavior of the 'fast' parameter, leaving significant opacity.

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 one sentence with no filler, which is concise. However, it largely restates the tool name and omits critical details, making it under-specified rather than elegantly concise.

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 one optional parameter, no annotations, and no output schema, the description is the only source of context. It fails to explain what the statistics contain, what the tool returns, or what 'fast' does, rendering it incomplete even for a 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?

The schema exposes a single optional 'fast' parameter with a union of types but no description. The tool description does not mention 'fast' at all, and with 0% schema description coverage, the agent has no way to understand its meaning or how to set it.

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 'Get WeFlow Moments export statistics' uses the specific verb 'Get' and identifies the resource as 'WeFlow Moments export statistics', clearly indicating the tool's function. It distinguishes from the sibling weflow_sns_export by focusing on statistics rather than the export itself, but 'statistics' remains somewhat vague.

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 provides no guidance on when to use this tool versus alternatives like weflow_sns_export or weflow_sns_timeline. There is no mention of prerequisites, timing, or how it fits into the export workflow.

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