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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety and side-effect profile are fully covered elsewhere. The description adds the scope of returned content, which is useful, but says nothing about locale fallback behavior, response shape, or whether missing facts are omitted versus null.

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?

A single front-loaded sentence that opens with the entity name and then lists content, so the reader learns what it is before the enumeration. The long content list is dense but every item carries information; no filler sentences.

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-required-parameter, read-only lookup with no output schema, the description's content inventory effectively stands in for a return-value description, so an agent knows what it will get back. The remaining gap is the locale parameter, which is unaddressed in prose.

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 is a single optional parameter, and the schema documents it at 100% coverage including the enum values (en, fa, ar, ckb) and a default. The description never mentions the locale parameter or what changing it affects, so it adds nothing beyond the schema — baseline 3 applies.

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 concrete resource (Barmaan company/contact facts) and enumerates the specific data it returns — phone, address, email, WhatsApp, map link, hours, social profiles, registration details. That makes it distinguishable from data-oriented siblings like get_product, list_projects and get_brochure, though it never states a verb or explicitly contrasts itself with them.

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?

The phrase 'use for ...' plus the itemized list gives a clear condition for invocation: any request about contact details, hours, registration or site links. However, it offers no exclusions or routing to alternatives — e.g. it does not say to use get_brochure for the actual brochure download versus this tool's brochure links.

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