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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered structurally. The description usefully adds that a placeholder identifier is 'acknowledged and discarded' rather than erroring, which is real behavioral context, but it omits auth/scope requirements and any note on result size or ordering.

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?

Two short sentences with the core action front-loaded and no filler. The second sentence is somewhat tangential to the tool's own purpose (it describes another tool's behavior), but it is genuinely useful and brief, so it does not seriously hurt readability.

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?

With no output schema, the description partly compensates by naming platformId, but it does not enumerate the other fields returned (account name, platform, connection status) or explain auth preconditions. For a read-only listing tool with annotations covering safety, this is adequate but leaves gaps an agent must discover by calling.

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 takes zero parameters, so the schema has nothing to document and the description is not required to compensate. It still adds value by naming the 'platformId' value the caller is expected to harvest from the result.

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?

States a specific verb and resource ('List connected social accounts') and even names the key field returned ('platformId'), so the agent knows what the call yields. It does not explicitly differentiate itself from adjacent read tools like account_context or company_channels, which keeps it short of a 5.

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?

Gives concrete downstream guidance: copy platformId verbatim for personal posts, and use 'publora-playground' with create_post for a publish-free connection test. However, it never says when to prefer this tool over siblings such as account_context or company_channels, so the selection guidance is only half-present.

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