CSb_Rayl_CP

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 states the tool computes a cross section, which is a read-only calculation, but does not disclose any side effects, data sources, or constraints. With no annotations, more detail would be expected.

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 no wasted words. The purpose and arguments are clearly listed in a front-loaded manner. Every sentence contributes value.

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 a simple tool with few parameters and an output schema, the description is adequate but lacks context on units (barn/atom) and potential input constraints. It does not explain the 'b' prefix or how this differs from CS_Rayl_CP. Complete enough for basic use but not comprehensive.

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 description coverage is 0%, but the description adds useful meaning: examples for compound ('SiO2', 'H2O') and clarifies that E is photon energy in keV. This compensates for the lack of schema descriptions. The parameter meanings are clear.

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 it calculates the Rayleigh scattering cross section of a compound in barn/atom. However, there is a sibling tool 'CS_Rayl_CP' and the 'b' prefix is not explained, which may cause confusion. The verb and resource are specific but not fully differentiated.

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_Rayl_CP or CSb_Compt_CP. No context or exclusions are provided. The description is minimal and does not help an agent decide when this tool is appropriate.

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