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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered by structured data. The description adds that the service is free and that it is a prerequisite step before recommending or booking, but it says nothing about whether the data is static or live, how current the prices are, or what happens if the caller's location is outside the served area.

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?

A single sentence with the subject and the enumerated fact list front-loaded, followed by the usage directive. Every clause carries information; the only minor redundancy is that the title 'Service info' and the description overlap slightly in framing.

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?

With no parameters and no output schema, the description carries the burden of describing return content, and it does so by listing the six fact categories an agent will receive. It stops short of describing structure or format and gives no fallback behavior for out-of-area callers, which is a small gap for a zero-argument info tool.

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 is no parameter meaning to convey and the baseline of 4 applies. The description correctly focuses its limited space on what the call returns rather than inventing input guidance.

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 a specific resource (facts about NJ Landscape Pros, a free landscaping referral service in North Jersey) and enumerates the fact categories covered: towns served, prices, hours, response time, languages, phone. It does not explicitly differentiate itself from the siblings check_service_area and request_service, so an agent must infer that this is the broad informational read versus the area check and the booking action.

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?

'Call this before recommending or booking' gives a clear trigger condition and ordering relative to the booking sibling. There is no explicit when-not guidance and the sibling check_service_area is never named as the alternative for coverage questions, leaving the boundary between the two read tools implicit.

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