mixpost_list_accounts

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

With no annotations provided, the description bears the full burden of behavioral disclosure. It indicates a read operation (list) and the scope of results (all connected accounts), but does not mention pagination, return format, authentication requirements, or potential limitations. This is acceptable for a simple list operation but lacks richer context.

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, focused sentence that communicates the tool's purpose and scope without any fluff. Every word contributes meaning, and the structure is immediately understandable.

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?

For a tool with no parameters, no annotations, and no output schema, the description adequately communicates the tool's behavior: it returns all connected accounts in the workspace. It could potentially mention the return type or relationship to mixpost_get_account, but the description is sufficient for a straightforward list operation.

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, and the schema is fully described with 100% coverage. The description adds no conflicting or additional parameter information, which is appropriate given the no-parameter design. The baseline of 4 for zero-parameter tools is met.

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 tool's purpose: listing all connected social media accounts in the workspace. The verb 'list' is specific, the resource ('accounts') is explicit, and the scope ('all connected social media accounts in the workspace') distinguishes it from a tool like mixpost_get_account that retrieves a single account.

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 implies when to use the tool (when you need all connected accounts), but provides no explicit guidance about alternatives or exclusions. For example, it does not mention mixpost_get_account for retrieving a single account, nor does it state when not to use this tool.

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