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

With no annotations, the description carries the full burden, and it does add genuinely useful context: authentication runs through the caller's OpenAny gateway credentials and billing/authorization are gateway-determined. It does not say whether the call is strictly read-only, how pagination behaves, or what happens when the domain is unknown, so the behavioral picture is only partially covered.

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 capability front-loaded and the credential/billing caveat second. No filler, though the terseness leaves obvious informational gaps rather than wasted words.

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 five-parameter read endpoint with no output schema and no annotations, the description covers purpose, auth, and cost but omits the shape of a financing event, pagination expectations, and the required company identifier. Adequate to select the tool, thin for invoking it confidently.

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 coverage is 80%, so the schema already explains limit, both first_seen_at bounds, and company_id_or_domain. The description adds nothing beyond that, and the one undocumented parameter (page) is left unaddressed, so it neither helps nor hurts relative to the baseline.

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 specific verb and resource ('Returns a list of company's Financing Events'), and the title reinforces it with 'funding rounds by domain'. It distinguishes itself from siblings implicitly through the resource name (connections, news_events, technology_detections are separate tools), but the description itself never contrasts 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?

There is no guidance on when to choose this over treg_get_call_predictleads_companies_news_events or the other PredictLeads company endpoints, and no prerequisites or exclusions. An agent must infer usage purely from the resource name.

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