calculate_net_pay

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

The description indicates a computation (no side effects), but with no annotations, it does not explicitly state read-only behavior. However, the text implies no data modification, providing adequate 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 concise, front-loaded with a summary, and well-structured with a bullet-like list for outputs and parameters. Every sentence adds value.

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?

Despite an output schema existing, the description lists return values. All parameters are explained, and default values are provided. The tool's behavior is fully covered for an agent to understand and invoke correctly.

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 description coverage, the description fully compensates by explaining each parameter (units, defaults, meaning) in the Args section, adding value beyond the schema's type and title.

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 'Determine net pay by applying porosity, Sw, and Vshale cutoffs to log data' with a specific verb and resource. It lists outputs and parameters, distinguishing it from sibling calculation tools.

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 implies use when net pay is needed from log data but does not explicitly mention when to use or avoid this tool, nor reference alternative tools among the many siblings.

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