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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses that reveals are rate limited per caller and should be requested sparingly. It also clarifies the distinction from get-venue's masked number, giving agents a clear behavioral model.

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?

The description is tightly organized with a purpose statement, an explicit when-to-use section, and rate-limiting guidance. Every sentence earns its place, and key constraints are front-loaded.

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 simple single-parameter tool, the description covers what the tool returns, when to use it, how to use it responsibly, and why it exists separately from get-venue. No critical guidance 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?

The schema already fully documents the only parameter, slug, as "The venue slug from search-venues." The description adds no additional parameter semantics, but the 100% schema coverage means no compensation is needed.

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 clearly identifies the tool as returning "The venue's real phone number," and explicitly contrasts it with get-venue, which "returns a masked number." This makes the tool's purpose and differentiator unmistakable.

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 provides explicit WHEN TO USE conditions: the user wants to call, often because the venue is not bookable online or a question isn't answered by profile fields. It also gives concrete constraints: request one at a time, for a chosen venue, never in bulk across search results.

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