DCS_Compt_CP

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

No annotations provided, so the description carries full burden. It only states the calculation and units, but does not disclose side effects, read-only nature, model assumptions, or valid parameter ranges. Minimal behavioral disclosure.

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?

Extremely concise: one sentence for purpose, then a brief list of parameters. No redundant words, fully front-loaded.

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?

With an output schema presumably documenting the return value, the description gives the essential context (purpose, units, parameter roles). However, it lacks details on valid compound formats, energy range, or relationship to sibling tools, making it minimally complete.

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 description coverage is 0%, but the description adds meaning by specifying that 'compound' is a chemical formula, 'E' in keV, and 'theta' in radians. This provides context beyond the bare schema, though constraints like allowable energy range are missing.

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 verb 'Calculate', the resource 'differential Compton scattering cross section of a compound', and includes units (cm2/g/sr). It distinguishes from siblings like DCS_Compt (likely for elements) via the '_CP' suffix and explicit mention of 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 on when to use this tool versus alternatives (e.g., DCS_Rayl, DCS_Compt). The description does not mention prerequisites or when not to use it. Given many siblings, explicit differentiation is lacking.

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