CS_Photo_Partial

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

No annotations exist. The description adds minimal behavioral context beyond the scientific calculation (e.g., no mention of side effects, auth, or edge cases). The presence of an output schema partially compensates for missing return value explanation.

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-line purpose followed by clear parameter definitions. Every sentence adds necessary information without waste.

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 scientific nature and existence of an output schema, the description covers the essential inputs and units. However, it could mention expected output format or error handling for invalid shells.

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?

Despite 0% schema description coverage, the description adds meaningful details: Z range (1-120), shell examples, and E unit (keV), going beyond the schema's bare types.

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 action ('Calculate') and resource ('partial photoionization cross section for a shell') with units (cm2/g), distinguishing it from siblings like CS_Photo and CS_Photo_Total.

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 provided on when to use this tool versus siblings. With over 80 sibling tools, explicit usage context is missing.

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