DCSb_Rayl_CP

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

No annotations are present, and the description does not disclose any behavioral traits such as valid energy/angle ranges, assumptions, side effects, or dependencies. For a scientific computation tool, this is insufficient.

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 extremely concise, with a one-line purpose immediately followed by a clear parameter list. Every sentence adds necessary information; no wasted words.

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 complexity of the domain and numerous sibling tools, the description lacks context about how this tool differs from similar ones (e.g., what 'b' or 'CP' means). An output schema exists, so return values are not needed, but limitations or prerequisites are absent.

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 critical semantic information: units for E (keV) and theta (radians), and an example for compound. This compensates for the bare schema titles.

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 the differential Rayleigh scattering cross section of a compound, including units (barn/atom/sr). However, among siblings like DCS_Rayl and DCS_Rayl_CP, it does not differentiate why this specific variant should be used.

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 alternatives like DCS_Rayl, DCSb_Rayl, or DCS_Rayl_CP. The description simply lists parameters without usage context or exclusions.

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