CS_FluorShell_Kissel_no_Cascade

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

No annotations provided, so description must carry full burden. Only states it 'calculates' a value; no disclosure of limitations, prerequisites, edge cases, or behavior beyond the calculation. Minimal behavioral insight.

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?

Extremely concise: two-line description plus argument list with no extraneous content. Every sentence serves a purpose.

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 complexity of domain with many sibling tools, description is minimal. Does not explain 'without cascade' distinction or return value (though output schema exists). Adequate but could provide more scientific context.

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%, so description must compensate. Description lists parameters and gives some meaning: Z with range (1-120), shell with examples, E with unit (keV). However, shell does not list all valid values, and no constraints on E. Adds some value but insufficient for full parameter understanding.

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?

Description clearly states verb 'Calculate', resource 'fluorescence shell cross section', method 'using Kissel', units 'cm2/g', and qualifier 'without cascade'. This precisely distinguishes it from sibling tools like CS_FluorShell_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?

No explicit when-to-use or when-not-to-use guidance, but the description and name imply it is for Kissel-based shell cross sections without cascade. Lacks exclusions or alternatives compared to similar tools.

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