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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description still adds real value beyond them: prices are ranges not quotes, the owner confirms time and final price, nothing is charged, and the call is free. These are business-semantics caveats an agent should relay to a user and are not encoded anywhere in the structured data. It does not cover failure behavior for an unknown slug, which keeps it from a 5.

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 sentences, front-loaded with the action and scope, then the returned fields, then the pricing caveats. The field list is dense but every item earns its place by telling the agent what comes back. Minor cost is the run-on colon list, which reads heavier than necessary.

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 only one required parameter, no output schema, and read-only annotations, the definition is nearly complete: it enumerates the returned content in lieu of an output schema and states the pricing/charge semantics. The remaining gap is error behavior for an invalid or unknown slug.

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 is a single parameter with 100% schema description coverage, so the schema already explains that slug is the 'Business page id from frontdoor_find_local_service'. The description's 'by slug' adds no format, pattern, or sourcing detail beyond that, so baseline 3 applies.

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 verb and resource ('Get one Front Door business profile') and immediately scopes it ('by slug'), then enumerates the profile contents: services, price ranges, service days, ZIPs served, license line, openings and booking contract. That makes it distinguishable from the sibling lookup/search tool frontdoor_find_local_service without opening either schema.

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 only implied: the schema note that the slug comes from frontdoor_find_local_service, combined with 'by slug' in the description, suggests a follow-up call after a search. The description itself gives no explicit when-to-use or when-not guidance, and never names frontdoor_request_booking as the alternative once the profile has been read.

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