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

With no annotations provided, the description carries the full behavioral burden and does substantial work: it discloses the heuristic nature, the pay-per-call cost, the required payment-signature header, and the error behavior that surfaces payment terms. It doesn't detail every edge case, but it covers the most operationally critical traits.

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?

Four sentences with zero filler: purpose, output breakdown, limitation, sibling routing, and payment requirement are each clearly separated. The most important information is front-loaded.

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?

Complete for the tool's complexity. All needed call information is present: what to pass, what the output contains, key limitations, alternatives, and monetization/auth behavior. No output schema exists, but the description conveys enough about return structure for an agent to interpret results.

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 100%, so the baseline is 3. The description reinforces that query is the draft text and context relates to platform/audience, but adds only marginal semantic value beyond the schema's own parameter descriptions.

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?

States a specific verb ('Score'), a clear resource ('a draft post before publishing'), and the exact output dimensions (emotion, specificity, novelty, shareability, best-fit platform). Explicitly distinguishes itself from siblings score-landing-page and generate-ab-test-variants, so an agent can route correctly.

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?

Provides explicit when-to-use context ('before publishing'), and names the alternatives with their trigger conditions ('For landing-page copy use score-landing-page; to generate test variants use generate-ab-test-variants'). Also clarifies the limitation ('heuristic prediction, not a reach forecast'), preventing misuse.

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