zernio_list_snapchat_profiles_for_connect

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

No annotations are provided, so the description carries the full burden. It describes a read operation ('list available profiles') but does not disclose side effects, error conditions, or rate limits. While 'list' implies non-destructive, the description lacks other behavioral details like pagination or response format.

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 sentence that conveys all necessary information without any redundant words. It is front-loaded and every part earns its place.

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 simplicity of the tool (one parameter, no output schema), the description is mostly complete. It explains the purpose and when to use it. However, it does not describe the output format (e.g., list of profile objects), which would help the agent fully understand the result. Still, it is adequate for most scenarios.

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 input schema already provides a description for the required 'profileId' parameter ('The Zernio profile ID from the OAuth flow'). The tool description adds no further meaning beyond what the schema provides. With 100% schema coverage, a score of 3 is appropriate.

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 verb 'list' and resource 'Snapchat profiles/accounts', and the context 'after starting Snapchat OAuth to choose which one to connect'. It effectively distinguishes from sibling tools like 'zernio_list_profiles' (internal Zernio profiles) and other 'list_X_for_connect' tools for different platforms.

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 a clear prerequisite: 'After starting Snapchat OAuth'. This tells when to use the tool, but it does not explicitly state when not to use it or mention alternative tools. However, the context is sufficient for an agent to understand it's part of a multi-step connection process.

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