CSb_Compt

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention any behavioral traits such as whether the calculation is for bound or free electrons, valid energy ranges beyond the parameter constraint, or any side effects. The brief description is insufficient for a tool with many similar siblings.

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 very concise with two sentences plus an Args list, no redundant text. It front-loads the main purpose. However, it could include more detail without becoming verbose, given the tool's complexity.

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 large number of sibling tools for various cross-sections, the description lacks detail on the specific variant (e.g., bound vs free). It does not mention the output schema or return value nature. The tool has an output schema, so the description need not repeat return values, but it still fails to specify output units or context.

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 input schema has 0% description coverage, so the description compensates by explaining Z as atomic number (1-120) and E as photon energy in keV. This adds meaning beyond the parameter names. However, it does not describe the units or format of the return value or any additional constraints.

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 Compton scattering cross section of an element in barn/atom, providing a specific verb and resource. However, it does not differentiate from sibling tools like CS_Compt, CS_Compt_CP, or CSb_Compt_CP, making the purpose slightly ambiguous.

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 given on when to use this tool versus alternatives like CS_Compt, CSb_Compt_CP, etc. The description lacks any context about prerequisites or situations where this tool is preferred.

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