set_social_meta

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

There are no annotations, so the description carries the full burden, and 'Disabled' is a critical behavioral disclosure: this tool should not be invoked directly. It does not detail what happens if called, but for a disabled tool the status itself is the primary safety-relevant signal.

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 one compact sentence that front-loads the most important information ('Disabled') and immediately provides a redirect. There is no wasted text or redundant restatement of the schema.

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 disabled mutation tool with no output schema, the description supplies the essential context: do not use it directly and route through a reviewed payload workflow. The only gap is that the reviewed payload workflow is not concretely identified, leaving some ambiguity for an agent.

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 adds no meaning or usage context for post_id, og_image_type, twitter_use_og, or twitter_image_type. The disabled guardrail makes calling unlikely, but parameter semantics are effectively 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 clearly communicates that the tool is disabled and is a mutation-type operation, but it never states what resource or property it mutates. An agent must rely on the tool name set_social_meta to infer the actual purpose, and the description does not distinguish it from sibling mutation tools.

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?

It explicitly warns that the direct tool is disabled and tells the agent to use a reviewed payload workflow instead. This is strong when-not-to-use guidance, but the alternative is not tied to a named sibling tool, so it is not fully actionable.

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