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

Annotations declare destructiveHint=true and idempotentHint=false, yet the description never says which actions are irreversible, whether actions toggle (unlike/unfollow), or what re-invoking does. For a tool with a destructive annotation, the description should add this context and does not.

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?

A single front-loaded sentence with no filler. It is short to the point of under-specification, but it is not padded or disorganized.

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, non-idempotent tool with a free-form nested params object and no output schema, the description leaves the most important details (per-action parameters, side effects) unstated. Complexity here demands substantially more disclosure than one sentence.

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?

Schema description coverage is 0% and the nested 'params' object is completely undocumented in both the schema and the description, so the agent cannot know what fields each action requires. The description merely re-lists the enum values (and omits mute/block/report behind the vague word 'moderate'), adding almost nothing beyond the schema.

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 states a set of interaction verbs (like, follow, subscribe, moderate) applied to posts/accounts, so the agent can tell this is a social-graph/content interaction tool rather than a content-creation sibling like socnet_post. It loses a point because 'resoc' is unexplained jargon and the affected resource is only gestured at as 'posts/accounts'.

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 choose this tool over siblings such as socnet_post or socnet_group, and no mention of prerequisites or exclusions. The agent must infer usage from the verb list alone.

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