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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds nothing behavioral on top of that — no indication of what data source is queried, whether it hits the network, or what the returned stats look like. It does not contradict the annotations, but it contributes no context beyond them.

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 and contains no padding beyond the vendor URL, so it is not verbose. However, the two sentences carry no front-loaded functional claim, so the brevity comes from under-specification rather than tight writing.

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 stats tool with no output schema, the description should at minimum say which platforms and metrics the stats cover. Instead it only identifies the vendor and package, leaving the agent unable to predict the return value before calling.

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, and the schema is an empty object with additionalProperties, so there is no parameter semantics for the description to explain. Baseline 4 applies; nothing in the description is needed or missing here.

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 only restates that this is a "social media posting" module and names the underlying npm package; it never says what the stats tool actually returns or measures. The name suggests posting statistics, but the description adds no verb+resource specification beyond that, and nothing distinguishes it from siblings like profullstack_social-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 when-to-use guidance, no prerequisites, and no mention of any alternative tool. The agent gets boilerplate sourcing information instead of any condition that would select this tool over its siblings.

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