weflow_sns_usernames

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

With no annotations present, the description carries the full burden of behavioral disclosure. 'List' implies a read-only operation, but there is no mention of return format, pagination, authentication requirements, or any potential side effects. The description lacks transparency about what happens when invoked.

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 unnecessary words. Every word earns its place, and the structure is perfectly concise for a zero-parameter list operation.

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 absence of annotations and output schema, the description should explain return values and provide more context about what 'WeFlow Moments publishers' are. It does not specify what is returned (e.g., usernames, profiles, IDs), nor does it clarify the tool's role relative to the platform. The description is too minimal to be fully self-contained.

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, so the baseline is 4. The description does not need to add parameter meaning since there are none. The schema already confirms no properties, and the description aligns without conflicting.

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 uses a clear verb 'List' with a specific resource 'WeFlow Moments publishers'. It distinguishes from siblings like weflow_sns_timeline (which lists moments) and weflow_list_contacts by focusing on publishers. However, it does not elaborate on what exactly 'publishers' means or what the output contains, slightly limiting specificity.

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 use this tool versus alternatives. There are no mentions of ideal scenarios, exclusions, or comparisons with sibling tools. The description only states the action without any contextual direction.

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