DCSPb_Rayl

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

No annotations are present, and the description only states the calculation's purpose. It does not mention side effects, input validation, error cases, or output characteristics, leaving the agent without important behavioral context.

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: one sentence and a bullet list of parameters. No fluff, front-loaded, and efficient for quick understanding.

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?

For a calculation tool with an output schema, the description covers the essentials. However, it lacks context on typical usage scenarios or potential pitfalls (e.g., units must be consistent), which would make it more complete for an AI agent.

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?

The description adds meaning beyond the schema by providing units (keV, radians) and valid range for Z (1-120). However, it does not specify valid ranges for theta and phi, which would further improve clarity.

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 polarized differential Rayleigh scattering cross section with units. However, among siblings like DCS_Rayl, DCSP_Rayl, and DCSb_Rayl, it does not explain the distinction provided by the 'Pb' prefix (likely barn units), leaving some ambiguity.

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 similar siblings such as DCS_Rayl or DCSP_Rayl. The user must infer from the name and description, which may lead to incorrect tool selection.

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