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

The description goes far beyond the annotations by disclosing that the tool is free, rate-limited to 3/hour per IP, uses the same sealed engine, and returns real Kirk output. It also details the synthetic nature of inputs and the return contents, providing rich behavioral context beyond the readOnlyHint/destructiveHint annotations. No contradiction.

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 long but well-structured with sections (Purpose, Use when, Do not use, Capability class, Cost, Returns). It front-loads the key summary in the first sentence and each subsequent section earns its place, though a slightly tighter presentation could improve scannability.

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?

Given the tool has no input parameters and an output schema exists, the description is highly complete: it covers purpose, usage guidance, cost/rate limits, and details the return object fields (per-class statistics, z-separations, provenance, etc.). This gives the agent all necessary context for correct invocation and interpretation.

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?

With zero parameters, the rubric gives a baseline of 4. The description reinforces this by stating 'Zero arguments' and clarifying that the inputs are fixed synthetic spectra baked into the demo, adding meaningful context about why no parameters are needed.

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 runs a curated Kirk demonstration on a UAV example, with zero arguments, and distinguishes it from siblings like kirk_infer_legacy and kirk_demo_trading by emphasizing its demo nature and fixed synthetic inputs. It also conveys the purpose: first-time users can see what Kirk does before signing up.

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?

Explicit 'Use when' and 'Do not use when' sections tell the agent to use this tool for cross-domain generalization demos without audio data, and to use kirk_infer_legacy directly for real feature vectors. This clearly differentiates from alternatives and prevents misuse.

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