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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is fully covered elsewhere. The description adds that results include recent changes and listings, which is marginally useful, but says nothing about pagination, result limits, or how the two modes behave. With rich annotations the lower bar applies, so a 3 is appropriate.

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?

A single front-loaded sentence that carries both operating modes without filler. It is dense but every clause earns its place; only a slight loss for packing two behaviors into one unpunctuated alternative makes it less than ideal.

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?

No output schema exists, so the description is responsible for signaling what comes back, and it does list profile/listings/changes at a high level. With no required parameters and a dual-mode contract, however, an agent still lacks guidance on ambiguous input combinations and on the shape or volume of the returned listings.

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 67%: query and locale are documented in the schema, but slug is not. The description compensates partially by identifying slug as an 'AiSeek slug' and tying query to name lookup. That adds meaning beyond the bare schema, but it does not explain the slug format or the interaction between the two modes, so it stays at 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 the resource (company) and enumerates what is returned: profile, listings, and recent changes, plus a name-search mode. That is a clear verb+resource statement an agent can act on. It does not, however, contrast itself against siblings like search_changes or latest_changes, which also surface change data.

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?

Two modes are implied: pass a slug to fetch one company's profile/listings/changes, or pass a query to get a list of matching companies. That is useful routing context. But it never says what happens when neither or both are supplied, nor when the name-match path is preferable to other search tools, so the guidance stays implied rather than explicit.

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