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

The annotations already disclose that this is a non-read-only, non-idempotent, non-destructive operation, so the description adds little behavioral context beyond implying a publish action. It does not explain visibility, permissions, rate limits, or permanence of posted content, and it does not clarify how upload_media differs behaviorally from text posting.

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 description is a single front-loaded sentence with no filler or repetition. Its brevity is efficient, though the same brevity leaves important operational details unstated.

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?

Given a required action enum, an untyped nested params object, and no output schema, the definition is too sparse to guide correct invocation. It names content types but does not explain action-specific parameter requirements or expected behavior, which is a significant gap for a multi-action publishing tool.

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 description only loosely maps its resource list to the action enum values. It provides no explanation of the required action field, the nested params object, or what parameters are expected for each action, leaving most parameter semantics undocumented.

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 specific verb, publish, and concrete resources, notes, media, quotes, and replies, targeting the social graph. It is clearer than a tautology, but it does not explicitly distinguish itself from siblings such as socnet_interact or socnet_page.

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?

The description gives no guidance on when to use this tool versus alternatives such as socnet_interact or socnet_group. There are also no exclusions or conditions for choosing among actions like post, reply, quote, or upload_media.

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