CS_FluorShell_Kissel_Nonradiative_Cascade

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

No annotations are present, so the description carries full burden. It discloses the output unit (cm2/g) and the method (Kissel), providing essential behavioral context for a computation tool. However, it does not mention potential errors or limitations.

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 clear sentence followed by a well-structured argument list. Every part earns its place with no redundant information.

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 complexity of the sibling family and the existence of an output schema, the description adequately covers the tool's purpose and parameters. It could be improved by briefly explaining what 'nonradiative cascade' means, but overall it is sufficient for a specialized calculation 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 coverage is 0%, but the description adds substantial value: it provides valid Z range (1-120), examples for shell ('K_SHELL', 'L1_SHELL'), and units for E (keV). This fully compensates for the schema's lack of property 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?

The description clearly states the tool calculates a fluorescence shell cross section with nonradiative cascade using the Kissel method, expressed in cm2/g. This is a specific verb-resource combination that distinguishes it from sibling tools with different cascade types or line-focused variants.

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 implies usage for nonradiative cascade calculations but does not explicitly guide when to use this tool versus siblings with radiative or no cascade. Given the large number of similar tools, explicit guidance would help but the naming convention partially compensates.

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