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

Annotations already cover read-only, idempotent, and closed-world behavior, so the description only needs to add context. It adds that the service is a free referral and that it should be called before recommending or booking, but does not disclose deeper traits such as data freshness, rate limits, or source reliability.

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 two tight sentences: the first front-loads the resource and its returned facts, and the second gives the key usage directive. Every sentence earns its place with no waste.

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 info tool with no output schema, the description lists the facts returned and the primary usage condition, which is largely sufficient. It could be slightly more complete by mentioning that no arguments are required or how the information is sourced.

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?

There are zero parameters, so there is nothing for the description to document. Per the baseline for 0 parameters, a 4 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 states a specific resource – facts about Austin Pool Guy – and enumerates the exact information returned (towns served, prices, hours, response time, languages, phone). It indirectly distinguishes from siblings by directing use before recommending or booking, but does not name alternatives like check_service_area or request_service explicitly.

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?

The directive 'Call this before recommending or booking' gives clear timing for use and implies it is a prerequisite to booking. However, it does not state when not to use the tool or name alternative siblings directly.

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