solnk_list_accounts

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

No annotations are provided, so the description must fully cover behavioral traits. It discloses the returned fields and implies a read-only operation. However, it does not mention auth requirements, rate limits, or whether the list is paginated. This is adequate but not thorough.

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 two sentences: the first states what the tool does and the fields returned, the second gives a clear usage directive. Every sentence is meaningful, no redundancy.

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 tool's simplicity (list operation, two optional filters) and no output schema, the description sufficiently covers the core functionality. It does not explain filtering behavior or sorting, but the context signals (2 enum parameters, no required params) make the tool straightforward.

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 has 2 optional parameters (platform, status) with enums. Schema description coverage is 50% (status has a description). The tool description adds no parameter details beyond the schema, so it meets the baseline but provides no extra value for parameter semantics.

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 action (list), the resource (user's connected social accounts), and the specific fields returned (id, platform, username, status, capabilities). It distinguishes from sibling tools like solnk_publish or solnk_list_publishes by focusing on account listing rather than publishing actions.

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 explicitly advises 'Call this first to get account_id values for publishing.' This gives clear context for when to use the tool. However, it lacks explicit exclusions or alternatives, so it doesn't fully meet the criteria for a 5.

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