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

Annotations already disclose readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds almost nothing beyond naming an npm package: for a login tool it says nothing about OAuth/credential flow, whether a browser or token is involved, what state is created, or whether a session/token is returned. Those are the behaviors an agent actually needs here.

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?

It is a single short sentence with no filler, which is structurally fine. However, brevity here comes at the cost of substance, and the one sentence it does contain points at posting rather than login, so the content is not well spent.

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 an auth entry point with openWorldHint=true and no output schema, the description should explain the authentication flow and what the caller gets back (session, token, redirect). Instead it only identifies a package, leaving the agent without enough context to invoke a login correctly.

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 declared parameters (empty object schema with additionalProperties=true), so the baseline of 4 applies. The description adds no parameter meaning, but there is nothing to explain and the schema is fully described at 100% coverage.

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 title and name say this tool logs a user in to a social platform, but the description calls it an "MCP module for social media posting" and cites the @profullstack/social-poster package. The stated action (posting) does not match the named action (login), so an agent reading only the description would select this tool for the wrong job. It names a domain but not the actual operation.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives, even though the sibling list contains many social-* tools (social-status, social-platforms, social-post) that could be confused with this one. The agent must infer entirely from the name that this is the authentication entry point.

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