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

Annotations already declare readOnlyHint=true, and the description corroborates with READ-ONLY / only-GET. Beyond that it adds real context: the FULL path including query string must be passed, and the return is parsed JSON. It omits error behavior for invalid paths and rate limits, so not a full 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 compact sentences, front-loading the escape-hatch purpose, then the read-only constraint, then the path format and return. Zero filler; 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?

No output schema exists, but the description covers the return ('parsed JSON') and the calling format, and the read-only profile is stated. What an agent might still need — error responses for malformed paths or undocumented endpoints — is absent, keeping it just short of complete.

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 parameter description already states the full-path-after-origin format, so the description largely restates it. It reinforces with a second example and the 'INCLUDING any query string' emphasis, but adds no syntax the schema lacks. Baseline 3 is correct.

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 (GET) and resource (any YCBM API path not wrapped by a dedicated tool), and explicitly frames itself as the escape hatch relative to the wrapped siblings like list_bookings or get_profile. An agent can tell immediately this is a raw passthrough, not another wrapped endpoint.

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?

"Any YCBM API path not wrapped by a dedicated tool" gives an explicit selection condition, and "only GET is allowed" excludes write usage. It does not name any sibling as the preferred alternative ('if you need bookings, use list_bookings'), so the routing is inferable rather than spelled out.

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