CSb_FluorShell_Kissel_Radiative_Cascade

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

No annotations are provided, so the description carries the burden. It indicates a read-only computation ('calculate'), which implies no side effects, but does not disclose potential constraints, data sources, or error conditions. This is adequate but minimal for a 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 extremely concise: one sentence plus an argument list. Every sentence is necessary and front-loaded with the core action. No superfluous content.

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 presence of an output schema (not shown) and no annotations, the description covers the essential inputs, output unit, and a basic example. It could mention valid shell-Z combinations or energy ranges, but it is sufficient for a well-defined computational tool.

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 0%, but the description compensates by explaining each parameter: Z as atomic number (1-120), shell with example values, E as photon energy in keV. This adds meaning beyond the schema types and enables correct usage.

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 verb 'Calculate' and the resource 'fluorescence shell cross section with radiative cascade', including units (barn/atom). It is specific enough, though it does not explicitly differentiate from sibling tools like CS_FluorShell_Kissel or CS_FluorShell_Kissel_Nonradiative_Cascade; the name already signals the radiative cascade variant.

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?

The description provides no guidance on when to use this tool versus the many sibling tools (e.g., CS_FluorShell_Kissel_no_Cascade). It lacks context for selection, such as scenarios requiring radiative cascade or conditions to avoid.

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