DCSPb_Compt_CP

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

No annotations provided, and the description does not disclose behavioral traits such as read-only nature, required permissions, side effects, or any constraints. The description only states the calculation purpose, offering no insight into behavior beyond that.

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 plus a structured list of four arguments. Each sentence or line adds necessary information without redundancy. The argument list is clear and front-loads the purpose.

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 tool's moderate complexity (4 parameters), existence of an output schema, and scientific domain, the description adequately covers the core functionality and parameter semantics. It lacks details on return value structure, but output schema presumably handles that. Missing are usage constraints or typical scenarios.

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?

With 0% schema coverage, the description compensates by providing brief explanations for each parameter: compound as 'Chemical formula, e.g. SiO2, H2O', E as 'Photon energy in keV', theta and phi with units (radians). This adds meaning beyond the schema's type-only definitions.

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 'Calculate the polarized differential Compton scattering cross section of a compound (barn/atom/sr)' which uses a specific verb and resource, and the name 'DCSPb_Compt_CP' differentiates from sibling tools like 'DCS_Compt' (likely for elements) and 'DCSP_Compt' (possibly for unpolarized). However, it does not explicitly contrast with siblings.

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, no prerequisites, no conditions for use. The description only states what it does, leaving the agent to infer usage context from the name and parameter list.

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