CS_FluorShell_Kissel_Radiative_Cascade

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

No annotations are provided, so the description bears full responsibility. It mentions that the tool calculates a cross section using the Kissel algorithm and radiative cascade, and gives units and argument ranges. However, it does not disclose any behavioral traits such as potential errors, performance, or output format beyond what the name implies.

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 clarifying the purpose, followed by a clean argument list. No unnecessary words, 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 domain complexity and many sibling tools, the description covers basic constraints but does not explain what the returned cross section value represents or how it might be used. While an output schema exists to fill some gaps, the description could be more complete for a broader audience.

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 input schema has 0% description coverage, but the description fully compensates by defining each parameter: valid Z range (1-120), shell examples ('K_SHELL', 'L1_SHELL'), and E units (keV). This adds essential meaning that the schema lacks.

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 'Calculate the fluorescence shell cross section with radiative cascade using Kissel (cm2/g)', which includes a specific verb and resource. However, it does not differentiate from sibling tools like CS_FluorShell_Kissel_Cascade or CS_FluorShell_Kissel_Nonradiative_Cascade, missing an opportunity to clarify the unique aspect of '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?

There is no explicit guidance on when to use this tool versus the many similar siblings. No when-to-use, when-not-to-use, or alternative suggestions are provided. The user must infer 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.