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

With no annotations, the description carries the full behavioral burden. It does add real value by disclosing that calls use the caller's OpenAny gateway credentials and that charges and authorization are gateway-determined — a billing/auth warning the schema cannot express. However, it says nothing about what a person record contains, behavior on unknown ids, or whether calls are idempotent/cacheable.

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 the core action front-loaded before the operational caveat. No filler, though the gateway sentence is somewhat boilerplate and could be compressed further.

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 one-parameter read tool without annotations or an output schema, the definition covers what the call does and the auth/billing context. It leaves unclear what a 'person information' payload includes and how failures surface, which matters more here because no output schema or annotations compensate.

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 required parameter, and schema description coverage is 100% — the schema already explains the id as 'the numeric `id` from a people search, lookup or email response' with a minimum of 1. The description adds no further constraints or format notes, so the baseline of 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 ('Gets person information') plus the identifier type ('by its CompanyEnrich ID'), which implicitly separates it from the sibling treg_get_call_companyenrich_people_email. It does not name or explicitly contrast any sibling, so it falls short of a 5.

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?

Usage is only implied: the tool retrieves a record once you already hold a CompanyEnrich id, and the schema hints where such ids come from. There is no explicit when-to-use statement, no guidance on what to do when the id is unknown (e.g., search or email lookup siblings), and no error/not-found guidance.

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