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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description goes beyond that by naming the external sources (own website, Wikidata, SEC EDGAR, RDAP, DNS) — signalling third-party lookups, variable coverage and latency — and by noting prices are returned 'with the date seen,' which discloses data-freshness semantics.

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?

The key phrase 'Company profile from a domain' is front-loaded, followed by an efficient comma-separated inventory of returned fields and a source list. It is one long run-on sentence, but every clause enumerates concrete output and none is filler.

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?

With no output schema, the description must carry the return contract, and it does so thoroughly by listing every returned field plus the underlying sources. Gaps are minor: no mention of caching, rate limits, or behavior when a domain is unknown or the company is not in Wikidata/EDGAR.

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 only one parameter and schema description coverage is 100%, so the schema already documents the domain format with an example. The description repeats the 'from a domain' input but adds no syntax or normalization detail beyond the schema, making the baseline 3 appropriate.

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 states a specific resource (company profile) and input (a domain), then enumerates the exact contents returned — summary, HQ, industry, SEC listing data, key pages, tech stack, domain age, AI-readiness. This scope makes it clearly distinguishable from siblings like company_changes, vendor_trust_profile, or email_domain_check without opening any schema.

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 implied by the field list and the named data sources, so an agent can infer 'call this to profile a company from its domain.' However, there is no explicit when-to-use or when-not guidance, and no routing to alternatives such as vendor_trust_profile for trust assessment or email_domain_check for mail-only lookups.

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