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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description goes well beyond them by disclosing the key behavioral truth: the meeting does not exist until the human confirms on the page, and the name/email must not be URL-encoded by the caller. This is exactly the kind of side-effect/authority disclosure an agent needs for a booking tool.

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 tool's output, then usage instructions, then safety constraints. Every sentence carries distinct weight; nothing is padding, and the length is justified by the high-consequence confirmation semantics.

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 fully describes the return value (URL plus separate name/email fields) and the confirmation workflow. An agent has everything needed to call it and to avoid misrepresenting the result.

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% and both parameters are documented directly in the schema with the same 'show them alongside the booking link' intent. The description adds no format, constraint, or edge-case detail beyond what the schema already provides, so the baseline 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?

The description states a specific resource and scope: 'the agency's booking URL for a 30-minute meeting,' and clarifies precisely what is returned (the URL plus the human's name and email as separate fields). An agent can distinguish this from other create/submit siblings 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?

It gives explicit operational guidance — hand the URL to the human and have them enter name/email on the booking page — plus a hard negative constraint ('never present a meeting as booked on the strength of this link alone'). It stops short of naming an alternative sibling, so it is a clear context rather than a routing decision, but the when/when-not framing is strong.

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