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

readOnlyHint=true is already declared in annotations, and "Read" is consistent with it, so no contradiction. The description adds one genuinely useful behavioral detail — that billing tokens and payment configuration are deliberately excluded, which signals a redacted/partial payload — but it does not address scope/permission failures or whether "selected" settings depend on account configuration.

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, zero waste: the positive content is front-loaded and the exclusion follows. Every clause carries information an agent would otherwise have to guess at.

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 no output schema, the description must carry the return contract, and it partly does by naming ID, name, and settings plus the exclusions. But "selected scheduling settings" is undefined — an agent cannot know which fields to expect or how to detect missing ones — which is a meaningful gap for the only documentation of the response.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline for a no-param tool applies. The scope word "authenticated" usefully clarifies that the target business is derived from the credential rather than supplied by the caller.

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 ("Read") and a specific resource ("the authenticated business"), and enumerates what comes back: ID, name, and selected scheduling settings. The resource is clearly distinct from the appointment/location/service/staff resources covered by every sibling tool, so an agent can route here without opening a 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 by the phrase "authenticated business" — the agent can infer this is the tool for resolving the current account context before calling the entity-specific siblings, but no when-to-use or when-not-to-use condition is stated and no alternative is named. The exclusion clause concerns returned content, not invocation guidance.

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