CS_Total_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 correctly indicates a read/calculation operation, but discloses no behavioral traits such as energy limits or permissions. With zero annotations, the description is adequate but not enriched.

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 one sentence followed by a clear parameter list with examples. Every element is necessary and front-loaded, with no wasted words.

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?

The description covers purpose and inputs, but does not explain output shape, valid energy ranges, or edge cases. Given the existence of many sibling tools for different cross sections, more context (e.g., compound requirements) would improve completeness.

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 coverage is 0%, yet the description explains that 'compound' is a chemical formula (with examples) and 'E' is photon energy in keV. This adds crucial meaning beyond the raw schema, fully compensating for the lack of schema descriptions.

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 states 'Calculate the total cross section of a compound (cm2/g).' It specifies the verb, resource, and units, and the name includes 'CP' (likely compound), distinguishing it from other total cross-section tools like CS_Total for elements.

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?

The description lists required arguments with examples, making inputs clear. However, it does not explicitly state when to use this tool over siblings like CS_Total (for elements) or CS_Total_Kissel_CP, leaving implied usage based on tool naming.

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