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

Annotations cover the safety profile (readOnlyHint=true) and the description does not contradict them. It adds real context beyond the annotation: an authentication/role prerequisite and a field-level preview of the response (pending request count, pending_rename, draft). It stops short of describing shape or edge cases, hence 4 rather than 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?

Three short sentences, front-loaded with the audience constraint and then the payload, with the exclusion last. Slightly dense with parentheticals but every clause carries information.

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?

Read-only tool with no output schema and one optional parameter; the description enumerates the key returned fields, states the auth prerequisite, and routes away from booking tools. Missing only error/empty-state behavior, which is minor here.

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 100% and the single optional business_id is already documented there, including the 'leave out when there is only one' rule. The description's note that business_id values originate here is useful chaining context but largely duplicates the schema text, 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?

Names the specific resource (owner's businesses and applications) and enumerates the concrete payload: pending requests count, pending_rename, unfinished draft. An agent can distinguish it from op_applications or owner_list_bookings without opening any 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?

Explicitly states when to call it ('use it first when the owner signs in or asks how things stand'), states the audience gate ('only for business owners signed in'), and names an exclusion with the correct alternative ('not for bookings (owner_list_bookings)'). Nothing is left to inference.

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