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

Although readOnlyHint=true is annotated, the description adds meaningful behavioral context by stating 'Books nothing itself; the person completes it.' This clarifies that the tool is a pure link provider and does not perform any action on the booking, going beyond the annotation.

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 short sentences convey the full purpose and the critical caveat about not booking anything. The information is front-loaded and every word earns its place.

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 zero-parameter, read-only tool with an output schema, the description fully covers what matters: what the links are for and what side effects do not occur. Nothing an agent needs to invoke it correctly is missing.

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?

There are zero parameters, so the schema already covers everything. The baseline of 4 applies because there is no parameter information needed and the description appropriately focuses on behavior rather than inputs.

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 precisely what the tool provides: links for a human to book a Tabflows demo or sign up. It distinguishes this from booking tools by explicitly saying it books nothing itself, making the resource and action clear.

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?

The description makes the context clear: use this tool when the human needs a demo booking or sign-up link. It doesn't explicitly name alternatives or exclusions, but the tool's scope is so distinct from siblings that little ambiguity exists.

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