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

No annotations are provided, so the description carries the full burden. It does add genuinely useful context that structured fields do not: the call is billed through the caller's OpenAny gateway credentials and charges/authorization are gateway-determined, which tells the agent this is a metered external call. It says nothing about error behavior for an invalid or unknown ID, rate limits, or what is returned.

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 short sentences with no padding, and the primary function is front-loaded. The first sentence is grammatically rough ('Gets a company information'), but nothing is wasted.

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 single-parameter read tool this is close to sufficient: purpose, identifier source, and billing/auth context are all present. Without an output schema, a brief indication of what the record contains (or of not-found behavior) would be needed to be fully complete.

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 the parameter already explains that the id is 'the UUID returned in the `id` field of any enrich or search result'. The description's phrase 'by its CompanyEnrich ID' aligns with that but adds no new format or constraint detail, so the 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?

States a specific verb and resource and scopes it to a lookup by CompanyEnrich ID, which distinguishes it from the search/autocomplete siblings. It does not, however, distinguish this from the closely named treg_get_call_companyenrich_companies_enrich or people_get siblings, which an agent would have to resolve from the tool name alone.

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 when-to-use or when-not-to-use guidance, and no mention of the sibling that performs enrichment. The only implicit cue is 'by its CompanyEnrich ID', which at least tells the agent an id must already exist, but nothing routes the agent between this tool and the enrich/search tools.

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