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

No annotations provided, but description discloses what the tool returns (plan name, description, price, etc.) and the two behavioral modes. Does not explicitly state it's read-only, but behavior is well-covered for a listing 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?

Three sentences conveying purpose, primary use case, and return fields. No redundant information, efficient and clear structure.

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 listing tool with one optional parameter, the description fully covers functionality, usage context, return data, and practical guidance. No missing aspects.

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?

Only one parameter, place_slug, with 100% schema coverage. The description adds significant context beyond the schema by explaining the difference between providing it or not and recommends its use.

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?

Clearly states it lists membership/subscription plans, distinguishes between listing venue-specific plans (with place_slug) and directory's own plans (without). The verb 'list' is appropriate and the tool is distinct from siblings.

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?

Explicitly recommends passing place_slug from search_places as the primary use case, warns that omitting it yields directory's own plans which most sites lack. Clear when-to-use and alternative.

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