Analyze Sale Triggers

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

Discloses an important behavior: it reports its own sample size first and explicitly warns when results may be noise due to insufficient data. It does not mention side effects, but the tool is clearly analytical and non-mutating in nature.

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 concise, front-loaded with the core purpose, and uses a second sentence to add important methodological detail and caveats without unnecessary fluff.

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 zero-parameter analysis tool, the description is complete: it states what is analyzed, which factors are considered, and how reliability is handled. Since an output schema exists, detailed return-value documentation is not required.

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?

The tool has no parameters and an empty input schema, so there is no parameter information to add. Baseline of 4 applies for zero-parameter tools.

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?

Clearly states the tool analyzes what correlates with fast vehicle sales in the user's own data, and distinguishes itself by listing the specific cross-referenced factors (days-on-market, price-versus-comps, price-drop history, vehicle type, price band, seller phrasing).

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 clear context for when to use it—when investigating sale-speed correlations in collected data—and includes a concrete reliability caveat about needing a few weeks of collection. It does not explicitly compare against sibling tools, but the usage context is clear.

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