weflow_sns_timeline

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It implies a read-only operation via 'Get', but does not mention pagination behavior, rate limiting, authentication requirements, or what constitutes a 'timeline entry'. No details about filtering, ordering, or response structure are given.

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, front-loaded sentence with no wasted words. It is concise, but it is under-specified rather than elegantly compact. It does not use bullets or structure, but that is acceptable given its brevity.

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?

The tool has 9 parameters, no output schema, and no annotations. The description is only 7 words long, providing no context about pagination, filtering options, return format, or integration with other tools. This is completely inadequate for a tool of this complexity.

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 description coverage is only 11% (only 'usernames' has a description). The tool description adds no parameter semantics at all—it doesn't explain start/end, limit/offset, media filters, or keyword. With 9 parameters and minimal schema descriptions, the description should compensate but does not.

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 states a specific verb ('Get') and resource ('WeFlow Moments timeline entries'), which clearly indicates this tool retrieves timeline data. It distinguishes from siblings like weflow_sns_export (export) and weflow_sns_usernames (usernames), though 'Moments' could be ambiguous.

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?

There is no guidance on when to use this tool versus alternatives. No mention of filtering, pagination relationships, or scenarios that would favor this tool over weflow_sns_export or other sibling tools. The description is purely definitional.

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