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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is known. The description adds no behavioural context beyond that: it does not say a real public post is created, whether it can be edited or deleted afterwards, what auth or platform connection is required, or whether calls are rate-limited. Naming the backing library is implementation detail, not behaviour.

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 clean. However, the brevity comes from under-specification rather than economy, and the one piece of content it does include, the package name, is the least useful detail for an agent.

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 destructive, open-world write tool with no output schema, the description should explain what is created and under what conditions. Instead it gives no payload guidance for an untyped free-form schema, so an agent must guess at argument names for an operation that publishes publicly and cannot be undone.

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 schema declares an untyped object with additionalProperties=true and no named properties, so it conveys nothing about what keys to send. The description does not fill that gap either, but with zero declared parameters the baseline expectation is already low, so this lands at a minimum-viable 3 rather than lower.

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 sentence 'MCP module for social media posting using @profullstack/social-poster' essentially restates the title 'Post to Social Media' and names an internal npm package. It never says what a post contains (text, media, links), which platforms are targeted, or how it differs from siblings like social-sample-content or social-validate-content, so an agent cannot confidently distinguish it from the rest of the social-* family.

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 precondition such as authentication (note the sibling social-login exists), and no statement of which sibling to call first. The description offers no criteria for choosing this tool over social-validate-content or social-posting-stats, leaving selection entirely to inference from the name.

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