MomentTransf

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

No annotations exist. The description is minimal and does not disclose side effects, performance, or assumptions. However, the tool performs a straightforward calculation, and the output schema likely documents return format. Additional context like units or range limits would improve transparency.

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 two sentences plus an argument list, front-loaded with purpose. Every word is informative; no fluff. Highly efficient.

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 no annotations and 0% schema coverage, the description is basic but covers the core functionality. It does not provide examples, range constraints, or mention the output format (though output schema exists). For a simple calculation tool, it is adequate but could be more informative, especially given the many sibling tools.

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%, so the description must add meaning. It clearly specifies that E is photon energy in keV and theta is scattering angle in radians, which is essential for correct usage. This compensates for the schema's lack of 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 clearly states the tool calculates momentum transfer for X-ray scattering, using a specific verb ('Calculate') and resource. It lists the two parameters with explicit physical meanings, distinguishing it from sibling tools like cross-section or energy calculators.

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 (e.g., ComptonEnergy or DCS_Compt). The description lacks context for tool selection among similar physics calculators.

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