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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered structurally; the description adds nothing beyond that. Worse, 'social media posting' evokes a write operation, creating tension with the read-only annotation, though it appears to describe the package rather than the tool's action.

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?

One short sentence, so there is nothing superfluous, but brevity here is under-specification rather than conciseness. Nothing is front-loaded about purpose, scope, or output.

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?

There is no output schema, so the description should explain what the status result covers (e.g. per-platform login state, account info). It does not, and it also fails to say whether any credentials or configuration are required, leaving the agent unable to predict the response.

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 there is no parameter semantics to document and the baseline of 4 would ordinarily apply. It is marked down slightly because the schema is fully open (additionalProperties: true), and the description gives no hint about what input — if any — might be passed through.

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 says only that this is an 'MCP module for social media posting using @profullstack/social-poster', which restates the package identity rather than a verb+resource. It conflicts with the tool name 'social-status' and title 'Social Login Status' — an agent reading the description alone would not know this reports login/connection status.

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?

No when-to-use guidance at all: nothing about when to call this versus social-login, provider_status, or social-module-info. The agent must infer selection from the tool name alone.

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