rewrite_content

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

No annotations are provided, so the description must disclose behavioral traits. It mentions the AI model ('Powered by DeepSeek V4 Flash') but fails to address important aspects like token limits, cost implications, reversibility, or handling of inappropriate input. The description lacks sufficient disclosure for a generative AI tool with no safety annotations.

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: a single introductory sentence, a usage sentence, and a formatted parameter list. Every sentence adds value, and there is no redundancy. It is front-loaded with the core purpose, making it easy for an agent to parse quickly.

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 tool with 5 parameters and an output schema, the description covers all parameters and the AI model, enabling correct invocation. It is missing potential details like output format (though output schema exists), rate limits, or maximum input length, but these are not critical given the output schema and parameter defaults.

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 tool description fully compensates by listing all 5 parameters with explanations, defaults, and enum-like examples for 'tone' and 'format'. The description adds meaning beyond the schema, such as the specific options for tone (professional, casual, persuasive, etc.) and format (paragraph, bullet_points, single_sentence).

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 states the tool's purpose: 'Rewrite content with AI — change tone, length, audience, or format.' It specifies the verb (rewrite), resource (content), and scope (AI-driven transformation). This distinguishes it from sibling tools like 'paraphrase' or 'simplify_text' which are more narrow in scope.

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 provides usage context: 'Use this to repurpose content for different channels' and mentions SEO, social media, and technical content adaptation. However, it does not explicitly say when not to use this tool or offer alternatives. No sibling comparisons or exclusions are given, so an agent might misuse it for simple paraphrasing when a specialized tool might be better.

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