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

With no annotations, the description does carry real behavioral weight: it discloses the payload breadth ('all 33 columns') and an auth-style prerequisite ('subscriber key'). It does not say what happens when the company is not found, whether the lookup is exact or fuzzy, or whether the subscriber key must be passed by the caller — and the schema has no such parameter, leaving that unresolved.

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 scope front-loaded and zero padding. The final clause is slightly cryptic in context but costs almost nothing in length.

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 description covers what is returned (33 columns) reasonably well. However, the dangling subscriber-key requirement — not represented in the schema — and the absence of not-found behavior leave the agent with an open question before invoking.

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 100% and the single 'company' parameter is already documented as 'Company name or website'. The description's 'by name or website' merely restates it, adding no format, matching, or ambiguity guidance (e.g., which wins if both could match).

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 resource and scope: the full record of one company, looked up by name or website. The singular 'One company's full record' implicitly contrasts with the plural siblings (leads, sample_leads), but it never names them, so differentiation is inferred rather than stated.

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 agent can infer this is a single-entity lookup versus the list-style siblings, but there is no explicit 'use this when... instead of leads/sample_leads'. The trailing 'Needs the subscriber key' hints at a prerequisite without saying what to do about it.

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