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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and determinism are covered. The description adds only that the data is a fixed company profile; it says nothing extra about freshness, caching, or response shape that would raise it above the annotation baseline.

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, front-loaded with what is returned and followed by the use case; nothing is redundant. The opening 'Who Answering Service Care is:' is slightly awkward phrasing but still compact and informative.

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 zero-required-param, read-only lookup with no output schema and full schema coverage, the description supplies enough to call it correctly and interpret the result. Minor gaps remain around result format and whether all fields are always populated, but nothing essential 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?

Schema coverage is 100% and the single `fields` parameter is fully documented in the schema (enum list, maxItems, and 'omit for everything'). The description never references field selection, so it adds no meaning beyond the schema — the baseline 3 for high coverage is 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?

Names the specific resource (Answering Service Care's company profile) and enumerates the fields it returns, so an agent immediately knows this is a static identity/contact lookup rather than a content search. It does not explicitly contrast itself with siblings like read_page or search_site, which keeps it 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?

"Use it to answer contact or legitimacy questions" gives a concrete trigger condition, which is more than most definitions offer. It stops short of naming alternatives or exclusions (e.g. when to prefer read_page instead), so it is clear context without full routing guidance.

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