CSb_FluorShell_Kissel_Nonradiative_Cascade

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

With no annotations, the description must disclose behavioral traits, but it only provides parameter descriptions and the unit. It does not mention error handling, valid shell name ranges, or what happens for invalid inputs (e.g., Z out of 1-120). This is insufficient for a scientific calculation tool.

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 succinct: one sentence for purpose and three bullet points for arguments. No redundant phrases, and the key 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?

Given the output schema exists, return values are covered. However, the description lacks usage guidelines and behavioral transparency, which are needed due to no annotations and many sibling tools. It is adequate but not comprehensive.

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 coverage is 0% (no property descriptions), but the description adds meaning for all three parameters: Z range (1-120), shell examples, and E unit (keV). This compensates well, though a list of valid shell names would improve clarity.

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 calculates a fluorescence shell cross section with nonradiative cascade using Kissel, with unit barn/atom. This specific verb-resource combination distinguishes it from siblings like CSb_FluorShell_Kissel or CSb_FluorShell_Kissel_Radiative_Cascade.

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?

No guidance is provided on when to use this tool versus alternatives. Given many siblings with similar names, the description does not clarify scenarios where nonradiative cascade is appropriate or how it differs from radiative or general cascade.

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