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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered. The description contributes nothing beyond that — no note on what the returned platform list looks like, whether it is a fixed catalog, or any limits.

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 short, but the space is spent on package naming and a vendor URL rather than on the tool's behavior. Concise in length, weak in allocation.

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?

This is a simple read-only catalog tool, but the one thing an agent needs — that it returns the set of social platforms supported for posting — must be inferred from the title. The description leaves the core output meaning implicit and offers no differentiation from profullstack_social-platforms.

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 nothing for the description to clarify about inputs and the baseline is 4. The permissive empty schema (additionalProperties: true) is a minor oddity but does not require description-side explanation.

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 text describes the module ('MCP module for social media posting using @profullstack/social-poster') and its hosting, but never states what this specific tool does. Only the name and title indicate it lists supported social platforms; the description is effectively boilerplate that restates the package context rather than a verb-plus-resource purpose.

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 conditions, and no mention of the closely named sibling profullstack_social-platforms, which an agent could easily confuse with this tool. The only context is the general 'social media posting' framing.

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