spectral_nbr

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

No annotations provided; description delivers formula, data range, and typical uses. For a non-destructive calculation, this covers behavioral expectations adequately. No contradictions.

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: first states purpose and definition, second provides formula and range, third lists applications. No unnecessary words; information is front-loaded.

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?

Covers purpose, formula, and applications. Lacks explicit statement of output format (single numeric value) but that is implied. Good enough for a simple calculation tool without output schema.

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 formula and use context but no new param-specific details beyond the schema descriptions.

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 calculates NBR from NIR and SWIR reflectance, provides the formula and range, and describes applications (wildfire burn severity, post-fire recovery, dNBR). Distinguishes well from sibling spectral indices.

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?

Describes when to use (burn severity, post-fire recovery) but does not explicitly contrast with other indices or provide when-not-to-use guidance. Context is clear enough for typical use.

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