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

Discloses behavior well beyond annotations: default date window, one-year maximum range, 50-result page cap, 10-page cap, and the meaning of response_size_limited and pagination_limit_reached. This tells the agent exactly how to handle partial pages and when to narrow filters.

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?

Every sentence earns its place: purpose, date defaults, pagination caps, and response flags. It is dense but not bloated, and the purpose is front-loaded before operational details.

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 an output schema present, return values need not be described in prose. The description covers the key invocation concerns: date defaults, pagination, and response flags. Minor gaps like exact date string format and explicit sibling routing are not spelled out, but they are recoverable from schema hints and tool names.

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 only 22%, so the description compensates by explaining date defaults, page size, page count, and cursor behavior. It does not enumerate every parameter, but enum-valued fields like dance, language, event_type, and salsa_style are largely self-describing, and the schema already documents location disambiguation.

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?

States a specific verb and resource: 'Find published salsa/bachata events for a location and dates.' It clearly distinguishes itself from siblings like get_event (single event retrieval) and search_locations (location resolution), so an agent can route correctly without reading schemas.

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?

Gives concrete invocation context: default UTC date range, the user-local-date exception for today/tonight, and pagination limits. It does not explicitly name alternatives or say when not to use it, but the operational guidance is clear enough for an agent to call it correctly.

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