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

With no annotations, the description carries the full burden and clearly states that the operation is read-only. It also explains the rentable filter behavior and lists the return fields, though it does not mention pagination, ordering, or any permission requirements.

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 front-loaded with purpose and filter guidance, then return values, and closes with the read-only note. Most sentences are useful, though the Stripe Connect parenthetical adds contextual detail that is not strictly needed for invoking the tool.

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 four-parameter search tool with no output schema or annotations, the description is fairly complete: it covers purpose, search modes, the rentable filter, return fields, and read-only status. It still lacks details on pagination, result ordering, and query/city interaction.

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 only 50%, so the description must compensate for undocumented city and query parameters. It indicates that query is free-text and city is a city filter, but does not clarify matching behavior, case sensitivity, or how the two parameters interact. Its description of rentable largely repeats the schema-provided meaning.

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 a specific verb and resource: search studios and gyms by free-text query or city. It is easy to distinguish from siblings like search_classes and search_mentors because the entity is explicit, though it does not explicitly name those alternatives.

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 explains the two search modes (free-text query or city) and when to pass rentable=true to restrict results. However, it gives no explicit when-not guidance, no mention of alternative tools, and no guidance on whether query and city should be combined.

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