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

With readOnlyHint/idempotent/destructive already declared, the description still adds rich context: `bookableViaFrontlatch`, `bookingNote`, `agentCallable` as evidence-not-permission, the `fallback` mechanism and that Frontlatch never sends the message, and the `counts.mappable` vs `actionable` distinction. The untrusted-content/security sanitisation rule (`untrustedContent`, `untrustedProvenance`) is a meaningful safety disclosure an agent would otherwise miss.

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 purpose is front-loaded in sentence one, followed by tightly packed field semantics and a security warning. It is dense but each clause earns its place (fallback behavior, counts, untrusted content); slight overloading of many symbols in one paragraph is the only cost.

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?

There is no output schema, so the description correctly steps in to explain return semantics (`bookableViaFrontlatch`, `bookingNote`, `fallback`, `counts`) plus the security posture. Nothing an agent needs to interpret or safely consume the result is missing.

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 description coverage is 100% with a single documented `business` param, so the schema does the heavy lifting. The description adds no syntax or format meaning to `business` beyond the schema's own note that it comes from find_business, matching the baseline 3 for high-coverage schemas.

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 first sentence gives a concrete verb and enumerates the resource's contents (phone, forms, booking links, widgets), so the agent knows it lists a business's detected actions. It is clearly a read/listing tool, distinct from do/do_action, though it never explicitly contrasts itself with sibling describe_action (which likely details a single action).

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 tool lists a business's actions, and the fallback/`counts` discussion hints at the decision surface, but there is no explicit 'use this when... / use describe_action instead when...' routing. No exclusions or alternatives are named.

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