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

No annotations are provided, so the description carries the full burden. It states the tool does not create a booking, implying no side effects, but does not disclose whether it modifies any state, requires permissions, or has rate limits. The description is adequate but minimal; a more explicit statement about read-only behavior would improve it.

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 long, front-loaded with the primary action, and contains no filler. Every word adds value, making it highly concise and well-structured.

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 46 parameters, high complexity, and no output schema, the description is too brief. It does not describe the output format (e.g., estimated price in what currency? Duration in what units? Is the estimate a range?), nor does it clarify parameter dependencies (e.g., lawn params only apply to Lawn-Care category). The description leaves significant gaps for an agent to use the tool correctly.

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%, so the baseline is 3. The description adds no additional parameter semantics beyond the schema. It does not explain parameter interactions or which parameters depend on the category or serviceType, which would be helpful for such a parameter-heavy tool.

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 calculates an estimated price and duration, and explicitly notes it does not create a booking, distinguishing it from sibling tools like create_order. The verb 'calculate' and resource 'price and duration' are specific and unambiguous.

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 explicitly says 'Use this during the quoting phase before the customer commits,' providing clear context for when to use it. While it does not explicitly list alternatives or when not to use it, the sibling tool set (especially create_order) implies the alternative for actual booking. The guidance is clear but could be more thorough.

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