CS_FluorShell

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

With no annotations, the description bears full responsibility for transparency. It only states the calculation and parameter constraints (Z range, shell examples, E in keV), but omits details about the underlying model, assumptions, or limitations. The behavior is implied but not explicitly disclosed.

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 concise: one sentence summarizing the function followed by parameter explanations in a clean bullet-like format. Every element serves a purpose with no redundancy.

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 large sibling family (many fluorescence cross section tools), the description lacks contextual completess. It does not explain the difference between shell and line cross sections, nor the significance of units or when multiple variants (e.g., with/without cascade) apply. The output schema existence is noted but not leveraged.

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, so the description must compensate. It provides useful context: Z range (1-120), shell name examples (K_SHELL, L1_SHELL), and energy unit (keV). However, it does not list all valid shell names or explain the meaning of shell designation, leaving gaps.

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 states the tool calculates 'fluorescence shell cross section (cm2/g)', which clearly identifies the physical quantity and distinguishes it from line or total cross sections among siblings. However, it does not explicitly differentiate from the similar CSb_FluorShell or other variants, leaving some ambiguity.

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 siblings like CS_FluorLine or CSb_FluorShell. The description only lists parameters without any conditional logic or context for selection, making it insufficient for guiding agent choice.

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