CSb_FluorLine_Kissel_Nonradiative_Cascade

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

With no annotations, the description carries the full burden. It discloses the formula (Kissel), the unit (barn/atom), and the cascade type (nonradiative). However, it does not describe output structure (though an output schema exists) or behavior on invalid inputs (e.g., invalid line name). It is adequate but not comprehensive.

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 very concise: one sentence plus a structured bullet list. It front-loads the main action. It could be slightly improved with better formatting (e.g., markdown), but it's efficient and easy to parse.

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 abundance of sibling tools and the existence of an output schema, the description covers the basics but lacks context on when to use this specific variant. It does not mention error handling or valid line names beyond examples. It is adequate for a simple tool but not fully comprehensive.

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 Args section adds meaning beyond the raw schema: Z is explained as 'Atomic number (1-120)', line includes examples ('KL3_LINE', 'KA_LINE'), and E is 'Photon energy in keV'. This compensates for the 0% schema description coverage and clarifies constraints and format.

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 line cross section with nonradiative cascade using Kissel (barn/atom).' It uses a specific verb ('calculate') and resource ('fluorescence line cross section'), and distinguishes this tool from siblings like CSb_FluorLine_Kissel_Cascade (which includes radiative cascade) and CSb_FluorLine_Kissel_no_Cascade by specifying 'nonradiative 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?

No guidance is provided on when to use this tool versus sibling tools (e.g., when to choose nonradiative cascade over radiative or no cascade). There are no explicit usage conditions or exclusions.

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