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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully carried by structured data. The description adds nothing behavioral — no mention of what the returned platform list contains, whether it is static, or whether auth is needed — and merely repeats vendor branding.

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 both sentences are spent on attribution and package naming rather than function. Nothing is front-loaded about what the tool returns or when to invoke 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?

With no output schema and no annotations explaining the return value, the description is the only place a caller could learn what "platforms" means (names, IDs, capabilities, supported content types) — and it says nothing. For a listing tool in a family of overlapping siblings, this is insufficient.

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 the baseline is 4; there is nothing for the description to disambiguate beyond the schema's open object.

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 describes the module ("MCP module for social media posting using @profullstack/social-poster") rather than stating what this specific tool does. Only the title hints that it lists social platforms, and nothing distinguishes it from the near-identical sibling profullstack_social-supported-platforms.

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 guidance on when to call this tool, when not to, or how it differs from profullstack_social-supported-platforms or the other social_* siblings. An agent has to guess which of the two platform-listing tools is appropriate.

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