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

Discloses that the tool does not fetch new data and reuses source stories and topic, providing context beyond annotations. However, it does not clarify whether the transformation creates a new content item or updates the existing one, leaving some ambiguity.

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?

Two concise sentences with no extraneous information. The key points are front-loaded, making it easy to scan.

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 an output schema likely covers return values, the description lacks detail on what 'transform' produces (e.g., a new content item?) and does not explain parameters. This leaves gaps for agent understanding.

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 coverage is 0%, yet the description offers no explanation of the three parameters (type, fromContentId, tieIn). The enum for type is hinted at by the example but not defined. This is a critical failing for usability.

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?

Clearly states the tool transforms an existing piece into another format, with a specific example (newsletter → tweet). This distinguishes it from sibling tools like betterpost_generate_content (which likely creates from scratch) and betterpost_humanize (which rewrites without format change).

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?

Describes context ('No fetching; reuses the source stories and topic'), implying it should be used when you have existing content to reformat. Lacks explicit when-not-to-use or alternatives, but the example and sibling tool names provide reasonable guidance.

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