Top rated companies

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, so the description only needs to add data semantics — which it does, explaining that the list is capped at 50 entries and that the rating is an average of employee reviews on a 1-5 scale. It omits any note on result fields or whether the list changes over time.

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 short, front-loaded sentences: purpose, use case, next step. The parenthetical gloss '(the site's "best companies" list)' mildly restates 'top companies by employee rating,' but the rest is waste-free and well ordered.

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 zero-parameter, no-output-schema list tool, the description covers what the list is, how the ranking metric is computed, its size limit, and where to go next. It never states what fields each company entry contains beyond implying an id, which is the one remaining gap.

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 takes zero parameters, so the schema-description baseline of 4 applies and there is nothing for the description to compensate for. The description uses the space instead to explain the output signal (rating derivation), which is a reasonable allocation.

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 gives a specific verb and resource ('List IranTalent's 50 top companies') plus the ranking criterion ('by employee rating'), which is enough to tell it apart from the generic it_companies sibling. It stops short of explicitly naming how it differs from it_companies, relying on the reader to infer that this is the curated/ranked subset.

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 names a concrete use case ('best places to work in Iran') and provides explicit next-step routing to it_company or it_company_reviews with the id. It does not state when not to use it or contrast directly against it_companies, so the alternative-selection guidance is clear but incomplete.

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