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

Annotations declare readOnlyHint=false and openWorldHint=true, so the agent knows this touches an external system and isn't a pure read. The description adds meaningful context beyond that: a 30-second throttle, a no-loop warning, and the downstream consequence of a 'connected' result. What's missing is any note on what a non-connected/pending/expired status means for the caller.

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 tight sentences, front-loaded with the core action and followed by the operational constraint. The parenthetical throttle note is compact and earns its place. Slightly dense phrasing ('the user reconnects or starts a new conversation') takes a moment to parse but carries real guidance.

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 does describe the return content (recent requests plus connected sites) and the conditional check on one pending request. For a one-optional-param tool this is largely sufficient, though the vocabulary of possible connection states is left undefined.

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 siteId is documented in the schema as 'Only this site (optional).' The description never mentions siteId or what narrowing to one site does to the response, so it adds nothing beyond the schema. Baseline 3 applies when the schema carries the parameter burden.

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 description opens with a specific verb+resource: it lists recent studio connection requests and connected sites, and checks one pending Mindbody request. That is clearly distinct from the write-oriented connect_studio sibling, though it never names that sibling to make the split explicit.

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?

It gives concrete operational guidance: call at most once every 30 seconds and don't loop. It also explains the follow-up action when a request reports connected (reconnect or start a new conversation so Mindbody tools load). It stops short of explicitly saying 'use connect_studio to initiate a new connection', which leaves one sibling routing decision implied.

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