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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by enumerating the returned content (founding date, social profiles, links), which matters because there is no output schema to reveal the shape of the response.

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 tight sentences: the first lists the payload, the second states the use case. Nothing is wasted and the returned-fields inventory is front-loaded where an agent will read it.

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 no-argument, read-only lookup with no output schema, the description carries exactly the burden it needs to: what data comes back and when to reach for it. Nothing required to invoke or interpret this tool correctly 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 and the schema is an empty object, so there is nothing for the description to disambiguate. Per the rubric, zero params sets the baseline at 4.

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 specific resource (Answering Service Care's identity/contact details) and enumerates exactly which fields come back: description, phone, email, postal address, founding date, social profiles, and key page links. That is far more concrete than a tautology like 'Get company info,' though it does not explicitly distinguish itself from siblings such as get_pricing or read_page.

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?

It gives a clear use condition — 'Use it to answer contact or legitimacy questions' — which tells the agent what class of user request this tool serves. There are no explicit exclusions or named alternatives, but the context is unambiguous for a zero-argument static-info tool.

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