Raw Mindbody GET (any endpoint)

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

Annotations already declare readOnlyHint=true, and the description is consistent with that (GET-only). It adds genuine behavioral context beyond the annotation: pagination semantics (paginate=true follows Limit/Offset pages), the PascalCase query-param convention, and that maxPages applies only with paginate. Error handling and rate-limit behavior are not covered.

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?

Front-loaded with the escape-hatch purpose, then progressively narrows to path examples, param naming, and pagination. Dense but every clause earns its place and nothing is repeated from the schema.

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?

For a raw passthrough GET with no output schema, the description gives enough to invoke it correctly: path format, param convention, and pagination behavior. Minor residual gap on error/response shape, acceptable given it is a generic forwarding tool.

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?

With 60% schema coverage, the description compensates well: it explains that query params are PascalCase (StartDate, ClientId, Limit), that m_... member tokens are accepted as values, and that paginate pairs with maxPages. It gives syntax/format guidance the schema omits for the 'params' and 'paginate' fields.

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 ('GET any Mindbody Public API v6 path with query params') and frames itself as the raw 'escape hatch' covering ~150 read operations. This explicitly distinguishes it from the typed per-resource siblings like mbo_get_client or mbo_get_staff.

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?

'Escape hatch' strongly implies fallback usage when no typed endpoint exists, and it tells the agent to set paginate=true specifically for list endpoints. It stops short of explicitly naming the sibling tools to prefer first or stating when NOT to use it.

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