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

With no annotations, the description carries the full burden and does so thoroughly: it discloses that output is based on training knowledge, figures are estimates, recent shifts may be missed, and it clearly explains the pay-per-call requirement and the error behavior when payment-signature is missing.

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?

Every sentence carries distinct value: output definition, use cases, data-source caveat, sibling routing, and payment/error behavior. The main result is front-loaded and the rest follows logically without padding.

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?

The description covers inputs, output shape, limitations, cost, error path, and alternative tool selection. No output schema exists, but the description sufficiently communicates what the agent should expect and how to invoke it correctly.

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 schema already documents both query and context. The description adds the top-5 output expectation and the general 'industry or topic' scope but does not materially explain parameter usage, nor does it clarify that query is effectively required despite there being no required field.

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 ('Name'), a precise deliverable ('top 5 marketing trends'), and the target scope ('for an industry or topic'). It further defines the output ('with a short description of each'), making the tool's function unmistakable and distinct from sibling tools like generate-marketing-strategy.

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?

Explicitly says when to use the tool ('Use for trend briefings and idea generation') and names the sibling alternative for adjacent needs ('For a full plan built on these, use generate-marketing-strategy'). Also gives a clear exclusion: it is not a live lookup and may miss very recent shifts.

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