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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is clear. The description adds the scope of returned business information but does not add further operational behavior such as freshness, caching, auth requirements, or return format, which is acceptable given the annotations.

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?

The description is a single, front-loaded sentence that lists the returned information without filler. Every listed item contributes to understanding what the tool provides.

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-parameter, read-only lookup tool with no output schema, the description supplies enough detail about the business and the categories of information returned. Combined with the annotations, an agent has sufficient context to select and invoke it correctly.

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 there are no parameter semantics to document. The description therefore does not need to compensate for schema gaps, and the baseline score for a parameterless tool 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?

The description clearly identifies the resource and enumerates the business details returned: contact details, hours, policies, credentials, and service area. It is specific enough for an agent to recognize the tool, but it does not explicitly differentiate itself from siblings such as list_service_areas, which overlaps on service-area information.

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 implied by the listed content: an agent can infer this is the tool for business contact, hours, policy, credentials, and service-area queries. However, the description gives no explicit when-to-use or when-not-to-use guidance relative to siblings like get_page, list_services, list_service_areas, or request_quote.

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