tickory_run_ad_hoc_scan

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

With no annotations provided, the description alone must convey behavioral traits. It states the scan runs immediately but omits details like output format, side effects, persistence of results, or authorization requirements, which is insufficient for a tool with 5 parameters and nested objects.

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 a single concise sentence that efficiently conveys the core function without extraneous words, earning maximum marks for brevity and clarity.

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 tool is complex with 5 parameters, nested objects, and an output schema, yet the description provides minimal context. It fails to explain the expression format, hard_gates purpose, or how to interpret outputs, and does not contrast with siblings adequately for a complete understanding.

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 description adds no parameter information beyond the input schema, despite only 60% schema coverage. It does not compensate for missing schema descriptions, leaving several parameters (e.g., builder_config, hard_gates) without clear purpose in the description.

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 executes a one-off scan immediately, distinguishing it from creating or modifying saved scans, which aligns with its name and differentiates it from siblings like tickory_create_scan and tickory_run_scan.

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 for ad-hoc scans by contrasting with saved scan operations, but does not explicitly name alternatives or provide when-not-to-use guidance, leaving room for clearer differentiation.

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