Get Oil Storage Levels

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

Annotations already declare readOnlyHint and openWorldHint, so the bar is lower. The description adds valuable context: it requires the Reservoir Mastery premium tier and states that it 'Returns current inventory levels with changes,' which goes beyond what the annotations provide.

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 three sentences with no wasted words. It front-loads the main purpose, then adds usage triggers, return behavior, and access requirement, all efficiently.

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?

For a simple one-parameter read-only tool, the description adequately covers purpose, when to use, return summary, and access requirements. It lacks a detailed return structure, but no output schema exists; still, the sibling overlap suggests more differentiation would improve completeness.

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 schema description for the single 'facility' parameter is complete, covering enum values, default, and descriptions. The tool description repeats similar facility information without adding new semantics, so baseline 3 is appropriate.

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 retrieves oil storage and inventory levels for Cushing and/or the SPR, using a specific verb and resource. However, it does not distinguish itself from the similarly named sibling tool 'opa_get_oil_inventories', which likely serves a similar purpose.

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 provides explicit usage context: 'Use when the user asks about oil inventories, storage levels, Cushing stocks, or the SPR.' This gives clear conditions to invoke the tool, though it does not mention when not to use it or suggest alternatives, especially given the overlapping sibling tool.

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