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

Annotations already declare readOnly, idempotent, non-destructive, and non-open-world behavior, so the safety profile is covered. The description adds genuine scope disclosure beyond that — that this reads static public material and never touches workspace or live records — which is useful for an agent deciding whether the answer is authoritative for a specific company.

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 sentences, no filler, with the positive scope front-loaded and the exclusionary scope second. Every clause earns its place.

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?

A parameterless read-only lookup with no output schema and full annotation coverage needs little more than what is given: the description says what content is returned and what is explicitly out of scope. Nothing an agent needs in order to call or trust it is missing.

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter syntax the description could usefully add. It appropriately spends its words on scope instead of restating an empty schema.

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 verb and resource — reading public EntityReach product information — and enumerates the content covered (capabilities, pricing, access requirements, limitations). It distinguishes itself from siblings only indirectly via the 'public' scope rather than naming a specific sibling tool, so it falls short of 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?

The second sentence provides an explicit when-not condition: it does not access a private workspace or live company records, which is exactly the boundary separating it from sibling tools that return company/group data. No alternative tool is named, keeping it out of 5 territory, but the usage context is clear.

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