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

With no annotations, the description must carry the behavioral load, and it does add real value by disclosing that the call uses the caller's OpenAny gateway credentials and that charges and authorization are gateway-determined — cost/auth context an agent would otherwise lack. It stops short of confirming read-only semantics explicitly, describing error behavior when neither id nor domain is supplied, or noting any rate limits.

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?

Two sentences, front-loaded with the return payload and followed by the cost/auth caveat. No filler; the gateway/charges sentence earns its place because annotations are absent. Minor oddity is the use of an em dash joined run-on for the field list.

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 low-complexity, two-parameter read with full schema coverage and no output schema, the description covers what is returned and the auth/cost model adequately. What is missing is selection context among a very large set of similarly named company-enrichment siblings, which is the main ambiguity an agent would face here.

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 100% and both parameters already state 'supply EXACTLY ONE of domain or id', so the schema does the heavy lifting. The description adds only 'for a single company', which is consistent with but not richer than 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 opens with a concrete verb and resource ('Returns workforce insights for a single company') and enumerates the payload — observed employee count, range bucket, and per-department headcounts — so an agent knows exactly what data this yields. It does not name sibling tools such as treg_get_call_companyenrich_companies_get or _enrich, so differentiation is by content rather than explicit routing.

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?

There is no statement of when to choose this over the many other treg_get_call_companyenrich_* tools (get, enrich, enrich_by_properties, people_get). The only hint is 'for a single company', which implies one-company-at-a-time but does not exclude or route to alternatives. An agent must infer selection from the returned fields alone.

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