calculate_bubble_point

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It mentions the correlation name and parameter units, but does not disclose assumptions, valid ranges, numerical stability, or other behavioral traits. For a correlation tool, details like input range limitations or mathematical behavior are missing.

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 structure: a one-line purpose followed by a parameter list. It avoids unnecessary words, though the parameter list partly duplicates schema information. It remains front-loaded and readable.

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 presence of an output schema (required by context signals), the description does not need to explain return values. However, it lacks typical usage context, valid input ranges, or the specific equation used. For a specialized correlation, more context would be beneficial but the basic information is sufficient for an agent to use the tool.

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 0% description coverage, leaving the description to add meaning. The description provides brief definitions and units for each parameter (e.g., 'Oil API gravity (degrees)', 'Reservoir temperature in F'), which significantly adds value beyond the schema's basic type and title information.

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's purpose: 'Calculate bubble point pressure using Standing's correlation (1947).' It provides a specific verb ('calculate'), a specific resource ('bubble point pressure'), and a distinguishing method ('Standing's correlation'), setting it apart from the many other 'calculate_*' sibling 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 offers no guidance on when to use this tool versus alternatives. It simply lists parameters without any context about prerequisites, typical use cases, or situations where it should be avoided. There are no instructions on when to choose this over other correlations or methods.

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