CSb_FluorLine_Kissel

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

No annotations available. Description implies a pure computation but fails to state read-only nature, required data availability, or any side effects. Minimal behavioral disclosure.

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?

Short description with purpose and parameter list. Every sentence contributes. Could be slightly more structured with separate sections, but sufficient.

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 40+ sibling tools and no output schema explanation, description lacks differentiation and does not cover edge cases, return format, or when to prefer this variant over others.

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 has 0% description coverage. Description adds meaning: Z range (1-120), line name examples, E in keV. However, does not specify valid line names fully or describe restrictions beyond examples.

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?

Clearly states 'calculate the fluorescence line cross section using Kissel photoionization' with units. Distinguishes from basic CS_FluorLine but not from other Kissel variants like CSb_FluorLine_Kissel_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?

Lists parameters with examples but provides no guidance on when to use this tool versus sibling tools for different Kissel cascade options or other calculation methods.

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