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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description adds value by detailing the output composition (content types, creators), default window, filter options, and cost (2 credits). It does not contradict annotations and provides meaningful context beyond the schema.

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 a single paragraph with no redundancy. It leads with the core function, includes the default window and cost, and ends with a usage hint. Efficient and front-loaded, though it could be tightened slightly.

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 5-parameter tool with no output schema, the description covers the primary purpose, usage scenario, default behavior, and cost. It does not explain the return structure or limit semantics, but the schema and description together give enough for a competent agent to make a call. Minor gaps exist but are not critical.

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 60%; query and timeFrame are described in the schema, and the description reinforces them ('Filter by keyword and platform', 'recent window (default one week)'). However, limit and platforms are not explained beyond the schema's basic types, and the description does not compensate for the missing parameter documentation. It adds some value but not comprehensive guidance.

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 ('Returns') and resource ('top overperforming posts in a niche'), and clarifies the scope (recent window, content-type breakdown, creator representation). It differentiates from generic search tools by emphasizing trend analysis and remixing, though it does not explicitly name a sibling alternative.

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?

It gives explicit usage context ('Great as the first call in a content-research loop') and suggests follow-up actions ('deep-dive or remix the winners'). It does not state when not to use it or name alternatives, but the scenario is clear enough for an agent to decide.

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