content_social_content_pipeline

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

The annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is conveyed structurally. The description adds useful context that execution is scoped by JWT, tenant, and company, and that this is a routing/dispatch wrapper. However, it does not describe what side effects the underlying social_content_pipeline action may have, leaving the agent to rely on the annotation alone.

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 compact and front-loaded with the core action, followed by a brief routing note and parameter list. There is no filler or irrelevant detail. It could earn a 5 if the parameter explanations added more operational value, but it remains appropriately concise.

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 an open-ended dispatch action with destructive annotations and a huge sibling list, the description is under-specified. It explains mechanics but not what social_content_pipeline actually does, when it is appropriate, what inputs are valid, or what side effects to expect. The output schema may describe returns, but the description still lacks enough context for correct selection and invocation.

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 schema has no property descriptions, so the description partially compensates by explaining message as a 'Free-text objective' and inputs as an 'Optional JSON string of structured inputs.' This gives a general semantic role for each parameter but does not describe what keys, formats, or values the pipeline expects in the inputs JSON. Given the 0% schema coverage, more specificity would be needed to make the tool confidently invocable.

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 action: 'Run the content domain agent action social_content_pipeline' and clarifies it routes through the platform's domain-agent dispatcher. It is clearly a generic invocation wrapper for a named domain action, though it does not explain what the pipeline itself accomplishes. It is more specific than a tautology, but it relies heavily on the tool name for meaning.

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 the many content_* siblings such as content_generate_content, content_schedule, or content_dispatch. It only describes routing mechanics and scope, not the conditions under which an agent should select this action. There are no when-to-use or when-not-to-use instructions.

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