content_repurpose

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

Without annotations, the description provides minimal behavioral context: it routes through a dispatcher under JWT/tenant/company scope. However, it does not disclose side effects, idempotency, rate limits, or output characteristics, which is insufficient for an agent to assess behavior.

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 short but inefficiently mixes routing details and parameter list. It could be more concise by focusing on action purpose and outcomes rather than implementation details like 'routes through the platform's domain-agent dispatcher'.

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 the tool's complexity (agent action with free-text goal and optional inputs), the description omits crucial context: what 'repurpose' achieves, expected output, and when it is appropriate. The existence of an output schema is not referenced, making the description incomplete.

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%, so the description must compensate. It identifies `message` as a free-text objective and `inputs` as optional JSON string, but lacks detail on expected format, constraints, or how they influence the action, leaving ambiguity.

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 'Run the content domain agent action `repurpose`', naming the specific action but not defining what 'repurpose' does. It fails to distinguish from sibling tools like content_generate_content or content_refine, making the purpose vague.

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?

No guidance on when to use this tool versus alternatives. The description lacks context for prerequisites, suitable scenarios, or exclusions, leaving the agent without decision support.

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