publer_list_accounts

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

No annotations exist, so the description carries full burden. It discloses no behavioral traits such as read-only status, authentication needs, rate limits, or side effects. Only the basic listing action is described.

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 very short and front-loaded, but it sacrifices completeness for conciseness. It could include more detail without becoming verbose, making it minimally acceptable.

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 simple tool (2 optional params, no output schema), the description is incomplete. It does not describe the return format, whether accounts are filtered by workspace, or what 'project default' means explicitly.

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?

With 0% schema coverage, the description must compensate but only vaguely mentions workspaceId or project default. It does not explain what projectPath is, how it relates to workspaceId, or the expected format/value range of either parameter.

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 lists social accounts in a Publer workspace. The verb 'List' and resource 'social accounts' are specific, and it is distinct from sibling tools like publer_list_posts or publer_list_workspaces.

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 hint 'Use workspaceId or a project default' provides minimal usage context but does not specify when to use this tool versus alternatives or when not to use it. No sibling differentiation or exclusions are mentioned.

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