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

Goes well beyond the readOnly/openWorld annotations by disclosing the privacy-relevant fact that no booking data reaches the server on this path, that the output is generated code (not computed results), and that the script writes revenue_plan.json and prints decision cards plus one line per product. These are exactly the side effects and trust considerations an agent needs before choosing this route.

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?

Three sentences, front-loaded with the size threshold that drives the routing decision, followed by output description and the data-privacy note. No filler and no repetition of the title.

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 an output schema present, return values need no further explanation, and the description still summarizes them. Combined with the explicit invocation thresholds, sandbox-write behavior and no-upload guarantee, nothing an agent needs to call this correctly is missing.

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% and each path parameter is already documented in the schema, so the baseline is 3. The description adds only that the engine reads products, fare classes, price history, bookings and show history, which largely restates the schema and says nothing about what 'params' must contain or what happens when optional paths are omitted.

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?

States a specific verb and deliverable: it returns a complete numpy-only Python script running the same engine as revenue_optimizer. The opening threshold clause immediately distinguishes it from its only sibling, so an agent can route without opening either schema.

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?

Gives concrete, numeric selection criteria (>500 products, >20,000 bookings, >5,000 price-history rows, or data already resident in the sandbox) and names the sibling that shares the engine, implying the in-server path for smaller payloads. The when-to-use condition is unambiguous rather than left to inference.

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