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

With no annotations, the description carries the burden. It does add useful behavioral context by disclosing the exact price ('3.0 USDC on Base') and pay-per-use model. However, it does not clarify whether the article input should be a URL, plain text, or markdown, nor does it explain response behavior or limits.

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 every part earns its place: purpose, input expectation, and pricing. Key information is front-loaded, with no filler or repetition.

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 single parameter and lack of an output schema, the description covers the core transformation and pricing but still leaves ambiguity around the input format and exactly how results will be returned. It is sufficient for a straightforward tool, though not fully complete.

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's input description is generic ('service input'), so the description adds meaning by specifying 'input=article'. This clarifies the expected semantic of the single parameter, going beyond the schema's minimal documentation.

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 verb ('repurpose'), a clear resource ('1 article'), and concrete outputs ('thread+LinkedIn+newsletter+TLDR'). This makes it easily distinguishable from generic siblings like summarize or rewrite-formal.

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 clearly implies when to use it: when you have a single article and want multiple repurposed formats. It does not explicitly state exclusions or alternatives, but the SMB framing and format list give adequate context for selection.

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