CS_FluorShell_Kissel_Cascade

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

With no annotations, the description must disclose all behavioral traits. It only states the calculation purpose and units. It does not mention computational complexity, input validation, error handling, or any side effects. The existence of an output schema is not leveraged in the description, and no behavioral constraints are provided beyond the basic operation.

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 extremely concise: one sentence for the purpose, followed by a bulleted parameter list. It front-loads the key action and units. No extraneous information is present, and every sentence serves a clear function.

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's complexity (part of a large family with many cross-section variations) and the absence of annotations, the description is minimally adequate. It states the calculation and units, but lacks details on output format, interpretation, or constraints like energy ranges. Since an output schema exists, it does not need to describe return values, but the description does not reference it or provide confidence in the result's shape.

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?

Input schema provides 0% description coverage, but the tool description compensates well: it explains Z as atomic number 1-120, shell with examples like 'K_SHELL' and 'L1_SHELL', and E as photon energy in keV. This adds meaningful context beyond the parameter names alone, though a more exhaustive list of valid shell names would improve it.

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 fluorescence shell cross sections with full cascade using the Kissel method, specifying units (cm2/g). Among many sibling tools with similar names (e.g., CS_FluorShell_Kissel without cascade, CS_FluorShell_Kissel_Nonradiative_Cascade, etc.), this description uniquely identifies the 'full cascade' variant, providing strong differentiation.

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 the many alternative cascade variations or other cross-section tools. The description does not mention when full cascade is appropriate, nor does it differentiate between radiative/nonradiative cascades or other outputs (e.g., CSb versions). This leaves the agent to infer usage from the name alone.

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