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 fully covered by structured data. The description adds no behavioral context of its own, and its "posting" framing is mildly at odds with a read-only listing tool, which could confuse an agent about side effects.

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, but its brevity comes at the cost of information rather than from tight editing. Nothing is front-loaded about what the tool returns or when to call it.

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 zero-parameter discovery tool with no output schema, the description should at minimum say it returns the list of supported platforms and how that list relates to social-post or social-supported-platforms. Instead it describes the underlying package, leaving the agent without enough to call it confidently.

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 meaning for the description to supply, and the schema is fully self-describing. Baseline 4 applies; nothing here is missing on the parameter front.

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 the tool is an "MCP module for social media posting using @profullstack/social-poster" but never states that it lists the social platforms supported for posting. It restates the module's general domain rather than this tool's specific verb+resource, and an agent would not know from this text what the tool actually does.

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 and no mention of alternatives, even though a close sibling named social-supported-platforms exists (judged only on this definition, the gap remains). The phrase "social media posting" only hints at the domain, leaving the agent to infer that this tool is the platform-discovery step.

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