CS_FluorShell_Kissel

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

No annotations are provided, so the description carries the full burden. It discloses the output unit (cm2/g) and calculation method (Kissel photoionization), but does not mention any constraints, thresholds, or edge cases. Lacks detail on behavior beyond what is stated.

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 with two sentences plus argument details, no wasted words. The purpose is front-loaded, and the arg list is clearly structured.

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 but exists), the description provides the essential purpose and parameter definitions. It lacks comparison with siblings and domain-specific context (e.g., valid energy ranges), but is adequate for a straightforward 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 meanings: Z is atomic number (1-120), shell is a shell name with examples, E is photon energy in keV. This compensates for the empty schema, though the exact format for shell (e.g., case sensitivity) is not fully specified.

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 fluorescence shell cross section using Kissel photoionization, with specific verb 'Calculate' and resource 'fluorescence shell cross section'. It distinguishes from siblings like CS_FluorShell (non-Kissel) and CS_FluorLine_Kissel (line vs shell).

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 on when to use this tool vs alternatives like CS_FluorShell, CS_FluorShell_Kissel_Cascade, or CSb_FluorShell_Kissel. The agent is left to infer selection from the name alone.

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