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

Annotations already establish that this is a safe read-only lookup, so the description correctly spends its words elsewhere: reviewer privacy ('initials only'), and the evidentiary detail attached to each review (sector, repeat account, deadline performance). That is real behavioral context beyond the annotations, though it doesn't describe result size or ordering.

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?

Three sentences, front-loaded with what the tool returns and closed with the user questions it answers. Every clause carries information; the parenthetical evidence list is the only slightly dense part, but it earns its place by explaining review structure.

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?

With no output schema, the description does the work of explaining what comes back: scores, profile links, and featured verbatim reviews with evidence tags. Combined with annotations covering read-only status, an agent has enough to call it correctly; only ordering or volume of results is unspecified, which is minor for a zero-parameter tool.

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?

There are zero parameters, so there is no parameter meaning for the description to supply. The baseline for a zero-param tool applies and nothing in the description misleads about inputs.

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 names a specific resource (customer reviews and platform ratings) and enumerates its contents: Google and Trustpilot scores, links to public profiles, and featured verbatim reviews. That is concrete enough to distinguish it from sibling tools like get_brand or get_company_facts without consulting either schema.

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 trigger phrasing — 'how good is Sense2', 'are they reliable', 'what do customers say' — which maps cleanly to the kinds of user queries that should select this tool. It stops short of naming a sibling as an alternative or explaining when-not to use it, so it misses the top bar.

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