get_pricing

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

Annotations already provide readOnlyHint=true and openWorldHint=true. The description adds useful behavioral context such as 'Takes into account emergency requests, weekend rates, and other pricing rules' and 'Always available for any business,' which goes beyond the annotation hints and clarifies the tool's behavior regarding special pricing conditions.

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?

Two concise sentences front-load the core purpose, with no filler. The second sentence adds valuable context about availability and pricing rules without redundancy.

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?

The description adequately covers the tool's purpose and key behavioral nuances, and the schema handles all parameter details. It does not describe the return format, but given the simplicity of the tool and absence of an output schema, this is a minor gap that does not impair selection or 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 100%, so baseline is 3. The description adds meaning by explicitly mentioning 'emergency requests' and 'weekend rates,' which maps to the isEmergency and requestedDate parameters, helping the agent understand how these parameters affect pricing beyond their schema descriptions.

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 clearly states the tool's function: 'Get a price quote for a specific service from a local business.' This is a specific verb+resource combination that distinguishes it from siblings like get_services (listing services) or book_appointment.

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?

The description implies usage context by mentioning emergency requests and weekend rates, but it does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions. The phrase 'Always available for any business' offers some guidance but lacks direct comparison to sibling tools.

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