DCS_Rayl

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

No annotations provided, and the description offers minimal behavioral context beyond the calculation itself. Does not disclose edge cases, interpolation, or limitations.

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 a clear main line and parameter list. No wasted words, though structure could be improved with a standard format.

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?

Lacks output format details, differentiation from many siblings, and any explanation of the physical calculation nuances. Insufficient for a non-trivial 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?

With 0% schema coverage, the description adds meaning: Z as atomic number (1-120), E in keV, theta in radians. This compensates for the bare schema, though ranges and units could be more explicit.

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 with units (cm2/g/sr), a specific verb and resource. It distinguishes from siblings like DCS_Compt and CS_Rayl.

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 versus alternatives like DCS_Rayl_CP or DCSb_Rayl. No prerequisites, when-not-to-use, or context for selection.

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