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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-schema context: this is a free third-party referral service rather than a contractor, which tells the agent how to represent the result. It does not mention rate limits or freshness of the facts.

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 front-loaded sentence that states the subject, the nature of the service, and the returned fields with no filler. Nothing in it is redundant or padded.

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 conveying what comes back, and it does so by enumerating the facts (towns, prices, hours, response time, languages, phone). Annotations cover the safety profile. Only minor gaps remain, such as whether prices are ranges or exact figures.

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. The description correctly implies a parameterless 'give me the facts' call without inventing any inputs, and adds nothing that would contradict the 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?

The description names a specific resource (Tulsa Foam Pros service facts) and enumerates the exact contents retrieved: towns served, typical prices, hours, response time, languages, phone. It implicitly separates itself from request_service via 'before recommending or booking,' but never names the other sibling check_service_area, so differentiation is only partial.

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 sequencing directive that positions it ahead of the request_service sibling. It stops short of stating when-not to use it or how it relates to check_service_area, so it is clear context without full exclusion rules.

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