get_refinement_options

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description adds that it returns 'attributes defined for the vertical with their possible option values, plus the universal serviceMode options' and explains the refinementAvailable flag behavior. This goes beyond the annotations to describe the output and conditional flow.

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 two sentences plus a conditional note, all front-loaded with the main purpose. No extraneous information; every sentence adds value by explaining usage, output, and integration with search_businesses.

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?

Given the tool has one parameter and no output schema, the description is complete: it explains what is returned (attributes, option values, serviceMode options) and the conditional refinementAvailable flag. Integration with sibling tools is clearly specified.

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 100% for the single parameter subCategory, which has a detailed description in the schema. The description does not add additional parameter semantics beyond what the schema provides, so a baseline of 3 is appropriate.

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 explicitly states 'List the refinement dimensions... available for a specific subcategory' and differentiates from sibling tools by specifying it should be called BEFORE search_businesses for broad queries. The verb 'List' is specific to retrieval, and the resource is clearly defined.

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?

Provides explicit guidance: 'Call this BEFORE search_businesses when the user's request is broad... so you can politely ask the user whether to narrow by any of these dimensions' and 'If refinementAvailable is false, skip refinement and go directly to search_businesses.' This covers when to use, alternatives, and conditional behavior.

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