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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool ranks trends but does not indicate whether it is read-only, what the output format looks like, whether it requires authentication, or any rate limits. The ranking criteria hint at behavior but do not cover side effects or operational constraints.

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 sentence that is front-loaded with the action and resource, followed by a list of criteria. It contains zero filler words and every phrase contributes to the meaning. It is appropriately sized for a tool with no parameters.

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 tool has no output schema and no annotations, so the description is the only source of behavioral context. It explains what the tool ranks and by which criteria, but does not describe the returned data structure, whether the ranking is ordered, or if there are any limitations (e.g., time windows, geographic scope). For a tool with this many ranking dimensions, an agent would benefit from knowing how results are presented.

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 tool has zero parameters and the schema is an empty object with additionalProperties true, so there is nothing to document. The baseline for 0 parameters is 4, and the description correctly avoids inventing parameter details. It adds no param-specific meaning because none exist.

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 clearly states the action (Rank) and the resource (TikTok trends), and lists specific ranking criteria (momentum, engagement, freshness, saturation risk, commercial relevance). It distinguishes from Instagram trends by name, but doesn't explicitly differentiate the scope or intended use case.

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?

No guidance is given on when to use this tool versus alternatives like instagram_trends or other sibling tools. There is no mention of use cases, exclusions, or prerequisites. The agent is left to infer when ranking TikTok trends is appropriate.

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