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

With no annotations provided, the description carries the burden for behavioral disclosure. It reveals a key behavior: falling back to the services list if no priced catalog exists. This is valuable behavioral context beyond the schema, though it doesn't mention permissions or side effects, which are less critical for a get operation.

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 sentences, with the primary purpose in the first sentence and the fallback behavior in the second. It is concise, front-loaded, and contains no redundant wording.

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?

Given the tool's simplicity (one parameter, no output schema) and clear scope, the description effectively covers the main functionality and an important edge case. It doesn't explicitly describe the response format, but 'services and pricing' and the fallback note give sufficient context for a straightforward retrieval 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 input schema has 100% coverage for the only parameter business_id, described as 'Business UUID.' The description adds no extra detail beyond the schema, so it gains no additional value. Baseline 3 is appropriate since the schema already documents the parameter.

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 uses a specific verb 'Get' with a clear resource 'services and pricing' and a target 'specific business.' It distinguishes from siblings like get_business or get_provider_details by focusing on services and pricing, making its purpose specific and clear.

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 description implies usage for retrieving services and pricing for a given business. It doesn't explicitly name alternatives or exclusions, but the fallback note clarifies behavior when a priced catalog is absent, providing clear context for use.

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