Get the booking widget embed

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

No annotations are provided, so the description carries the burden. It explicitly states 'Read-only; does not consume credits,' adding key behavioral context. It doesn't disclose error handling or rate limits, but for a read-only resolve operation this is adequate.

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: first states the action, second gives a direct usage instruction. Front-loaded and free of unnecessary detail.

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 low complexity (1 param, no output schema) and no annotations, the description covers purpose, usage, and safety (read-only). It lacks explicit prerequisites or failure modes, but those are not essential for a retrieve-embedding 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?

Schema coverage is 100% and the schema fully documents service_id. The description only refers to 'a bookable service' without adding additional parameter meaning beyond the schema.

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?

Description uses specific verb 'Resolve' and identifies the resource (embed HTML + script URL for a bookable service). It clearly distinguishes from sibling tools that manage other entities by focusing on the widget embed.

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?

Provides usage context ('Drop the returned embed_html into the page where the booking flow should appear') but doesn't explicitly compare to alternatives or state when not to use. The read-only note implies a retrieval use case, but sibling differentiation is absent.

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