get_pricing

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

Annotations indicate readOnlyHint: true and openWorldHint: true, which align with the description's 'Get a price quote' (read-only). The description adds beyond annotations by specifying that the tool accounts for emergency requests and weekend rates, giving behavioral transparency about pricing rules.

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?

Description is two sentences: first sets the purpose, second adds key details. No extraneous words, front-loaded with the action. Every sentence earns its place.

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 read-only pricing tool with 4 parameters and no output schema, the description covers essential context: purpose, special pricing rules, and general availability. It omits specifics on the return format, but given annotations and the tool's simplicity, this is acceptable. Slightly higher would require mentioning that pricing may vary or that the response includes a quote object.

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 all 4 parameters. The description adds significant value by instructing to copy the slug verbatim from search_businesses or get_business_info, and by contextualizing the isEmergency and requestedDate parameters with mentions of emergency requests and weekend rates. This helps the agent use parameters correctly.

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?

Description clearly states 'Get a price quote for a specific service from a local business.' The verb 'get' paired with resource 'price quote' is specific. It distinguishes from sibling tools like book_appointment, check_availability, etc., which focus on booking or availability, not pricing.

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?

Description provides context on when to use by mentioning 'takes into account emergency requests, weekend rates' and 'always available,' implying this tool handles special pricing scenarios. However, it does not explicitly state when NOT to use it or suggest alternatives, but the context is sufficient for most use cases.

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