calculate_brine_pvt

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

No annotations provided. Description only lists inputs and outputs but does not disclose any behavioral traits such as assumptions, error conditions, or required data quality. For a calculation tool, more transparency is needed.

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?

Description is concise with a clear subject line and a structured Args section. It could be more streamlined, but no unnecessary content.

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 output schema exists, the description adequately covers inputs and outputs. The tool is simple, and the description is sufficient for understanding basic functionality.

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?

Description adds meaning beyond the schema by stating units (F, psi, ppm) and default for salinity. This compensates for zero schema coverage, though input ranges or validation hints 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?

Description clearly states that the tool calculates brine/formation water PVT properties, listing outputs (density, viscosity, FVF, compressibility). It distinguishes itself from siblings by specifying the fluid type.

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 explicit guidance on when to use this tool versus other PVT calculation tools. Usage context is implied by the name and description, but no alternatives or exclusions are mentioned.

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