content_repurpose

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

The description mentions routing through the domain-agent dispatcher with JWT, tenant, and company scope, which is a behavioral detail. However, it does not disclose the actual effects or side effects of the repurpose action beyond what the annotations already state (destructiveHint true).

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 concise and well-structured: two sentences explain the action and routing, followed by a clear list of arguments. No redundant information.

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?

While the description gives the basic purpose and parameters, it omits details about the action's behavior, expected output, or how to formulate the message and inputs effectively. Given the existence of an output schema (not shown here), more context might be helpful for an agent to use it correctly.

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 description provides brief explanations for both parameters: message is a free-text objective, inputs is an optional JSON string of structured inputs. It adds some meaning beyond names but lacks detail on expected format or content of the JSON.

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 it runs the content domain agent action 'repurpose' and routes through a dispatcher. It names the specific action, but does not explain what repurposing entails or what the action accomplishes, so clarity is moderate.

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 use this tool versus alternatives. It does not mention scenarios, prerequisites, or contrast with sibling tools like dispatch_domain_agent or invoke_tool.

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