One researched company

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered upstream. The description's real contribution is disclosing the return payload in detail, which matters because there is no output schema. It says nothing about what happens when the domain is unknown or the company has not been researched yet — likely the most common failure mode.

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?

One tight sentence, front-loaded with the scope ('Everything recorded about a company') and then the enumeration. No filler. Minor deduction because it is a noun fragment with no verb, so the retrieval action itself is only implied.

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 with no output schema, the listed return fields largely substitute for a schema. However, it omits not-found / not-yet-researched behavior and any hint about response size or structure, leaving an agent unsure what an empty or partial result looks like.

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?

Single parameter with 100% schema description coverage ('Domain or website'), so the schema already does the work. The description adds no format guidance (bare domain vs full URL, whether www is allowed) beyond what the schema states, which is the baseline for full-coverage schemas.

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?

Names the resource (a company) and enumerates exactly what comes back — pages read, technologies, facts, catalog options, offer draft, publish status. That is far more specific than 'gets a company'. It never distinguishes itself from the confusable siblings get_company_context or research_company, which is the only thing keeping it from 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?

There is no when-to-use statement, no prerequisites, and no named alternative. An agent looking at get_company vs get_company_context vs research_company vs list_companies gets no routing help from this text whatsoever; usage is only inferred from the enumerated return contents.

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