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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that—no indication of what data is returned, what time window is covered, whether authentication/session state is required, or what happens with zero parameters.

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?

The single sentence is short but spends its words on library provenance rather than on the tool's behavior. This is under-specification rather than genuine conciseness, and the one useful fact (that it reports stats) is never stated.

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?

There is no output schema, so the description is the only source of information about return values—yet it says nothing about what the statistics contain, their granularity, or their format. For a zero-parameter read tool, that is a significant omission an agent would have to discover by trial.

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 semantics burden; the baseline of 4 applies. Nothing in the description misleads about inputs, and additionalProperties=true means the empty schema is not a hidden trap.

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 restates the module/library ('MCP module for social media posting using @profullstack/social-poster') rather than stating what the tool itself does. The tool name says 'stats', yet the description never mentions what statistics are returned or for which accounts/posts, so an agent cannot distinguish its purpose from siblings like social-post or social-status.

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 such as social-status or social-post. The description gives an agent no basis for choosing 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.