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

Annotations already cover the safety profile (readOnly=false, destructive=false, idempotent=true, openWorld=true), and the description adds the genuinely non-obvious part: this is a two-phase flow requiring the business owner to approve in Mindbody, with divergent outcomes (activation link/code, sent for review, or already owned by another account). It does not discuss what happens on repeated calls or the live-ness/lifetime of the returned code, but the external-approval behavior is disclosed well.

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 compact sentences ordered as purpose, eligibility, outcomes, then next step. The routing to the sibling tool is front-loaded at the end rather than buried, and no sentence is redundant with structured fields.

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 carries the return-value burden and does so by enumerating the three possible outcomes and the next call. For a single-parameter mutation with annotations covering safety, nothing an agent needs before invoking 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%: the single siteId parameter has its own description, example, and pattern. The tool description adds no further meaning about the parameter (e.g., where to obtain the Site ID), so the baseline of 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?

States a specific verb and resource ('Starts connecting a Mindbody business (site) to the user's StudioVector account') and explicitly distinguishes itself from the sibling studio_connection_status, which it names as the follow-up step. An agent can tell what this initiates without opening the 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?

Gives an explicit audience precondition ('For owners and admins of an account with an active plan') and a clear sequencing rule ('Then call studio_connection_status'). It does not address what to do if the caller is not an owner/admin or if a connection already exists, which keeps it short of a full when/when-not treatment.

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