CSb_Photo_Partial

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

Description provides basic behavioral info: inputs (Z, shell, E) and output unit (barn/atom). However, no details on error handling, validation, or edge cases. Since no annotations are provided, the description carries the full burden.

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?

Concise and front-loaded. Every sentence is useful: one-line purpose, then clear argument list. No unnecessary text.

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, the description adequately covers inputs and output units. Could note return value structure but output schema handles that. Minor gap: no mention of valid energy range or shell format.

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?

Parameter descriptions are minimal: Z range (1-120), shell example (K_SHELL), E unit (keV). The input schema has 0% coverage, so description partially compensates but lacks full specification of valid shell names or value constraints.

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 the tool calculates partial photoionization cross section for a shell, with units barn/atom. It distinguishes from siblings like CS_Photo_Partial (similar name) and other cross-section tools.

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 guidance on when to use this tool vs alternatives. Usage is implied from the description, but no when-not-to-use or comparison to similar tools like CSb_Photo.

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