DCSP_Rayl_CP

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

No annotations exist, so the description carries full burden. It does not disclose any behavioral traits such as being read-only, required permissions, side effects, or assumptions. It only states what it calculates, not how it behaves.

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: one sentence for purpose followed by a clean list of arguments. Every sentence adds value with no redundancy.

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?

Although output schema exists (so return values may be documented there), the description lacks context about when to use this specific variant (_CP) over siblings, and does not cover edge cases or typical usage patterns. It is adequate for a simple calculation tool 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?

The description adds meaning by specifying units (keV, radians) and format for compound (chemical formula). Schema coverage is 0%, so the description compensates significantly. However, it lacks constraints or ranges for parameters like E, theta, phi.

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 'polarized differential Rayleigh scattering cross section' with a specific verb 'calculate' and resource, and includes units. It distinguishes from siblings like DCS_Rayl and DCSP_Rayl by specifying polarization and compound.

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 the many sibling tools (e.g., DCS_Rayl, DCSP_Rayl). The description does not mention prerequisites, limitations, or context for invocation.

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