calculate_bubble_point

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

No annotations are provided, so the description carries the burden. It mentions the correlation and inputs but does not disclose assumptions, limitations, or side effects. Since it's a calculation tool, no destructive actions are expected, but transparency is moderate.

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, with a clear first sentence stating the purpose followed by a parameter list. It avoids unnecessary words, though a more structured format (e.g., separating description and parameters) could improve readability.

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?

While an output schema exists (not shown), the description does not explain the return value or typical output format. For a calculation tool, this omission may require the agent to rely on the schema. Edge cases or input constraints are not mentioned.

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?

The input schema has only titles (e.g., 'Api Gravity'), but the description adds units and explanations for all four parameters (e.g., 'Oil API gravity (degrees)'), compensating for the 0% schema description coverage and providing essential context for correct invocation.

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 'Calculate bubble point pressure using Standing's correlation (1947).' This specifies the verb, resource, and method, distinguishing it from many other calculate_* tools like calculate_gas_z or calculate_brine_pvt, which target different properties.

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 does not provide explicit guidance on when to use this tool versus alternatives or mention conditions like pressure ranges. The purpose is implied, but no when-not-to-use or alternative tools are listed, leaving the agent to infer from the tool name alone.

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