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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety and mutability are covered structurally. The description adds the content scope but says nothing about auth requirements, rate limits, or how the entity id is obtained; with rich annotations this is an adequate but not additive disclosure.

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 short clauses, zero filler, with the resource and its contents front-loaded. Every phrase contributes meaning.

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 an output schema present, the return values need no further explanation, and annotations cover the safety profile. The remaining gap is procedural: an agent still doesn't know where to obtain business_id, which matters for a single-parameter tool with no schema documentation.

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?

Schema coverage is 0% for the single business_id parameter and the description never explains it — not its format, nor that it likely comes from find_businesses. The phrase "a business's booking page" only implies an id is needed, which the schema already enforces.

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?

States a specific verb and resource (read a business's booking page) and enumerates what comes back: services with ids, prices, hours rules, and booking instructions. It is clearly distinct from find_businesses, though it does not explicitly contrast with list_services, which also surfaces services.

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?

"Read this first" gives a clear ordering directive that tells the agent to call this before book_appointment/check_availability. No when-not guidance or named alternative is given, but the sequencing context is unambiguous.

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