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

Goes well beyond the readOnly/idempotent annotations by disclosing the FREE-BY-DEFAULT booking model, including the critical interpretation rule that a large result means 'nobody blocked that day' rather than 'everyone is free'. It also states each result carries the `id` downstream tools need, and that output is paginated.

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 purpose, then the caveat, then the return contract, then filters and pagination. Dense but nearly every clause carries information; the act_type enumeration duplicates the schema slightly but is defensible as an error-prevention measure.

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 takes on the return-value burden and does so: it explains what each result contains (the member `id`) and how to read the result set size. A 5-parameter search tool with one required param is fully specified for correct invocation.

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 coverage is 60%, with limit/offset carrying no descriptions. The description compensates by flagging pagination and the optional city filter, and it restates the act_type allowed values, which reduces the chance of an invalid enum value being sent. It still adds no syntax or format detail for the pagination parameters.

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+resource+scope: artists/bands open to a booking on a specific date. It is instantly distinguishable from siblings like search_available_venues and check_member_availability, and the title reinforces the date-specific framing.

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 clear usage context by naming the downstream tools that consume the returned `id` (make_offer, check_member_availability), which implicitly tells the agent this is a discovery step, not a confirmation. It also warns the result is 'not a confirmed yes', steering toward check_member_availability. However, it never explicitly states when to prefer this over a different search or what the follow-up sequence should be.

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