OilPriceAPI

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

No annotations provided, so description carries full burden. Adds value by disclosing return structure ('totals and regional breakdown') but omits other behavioral traits like rate limits, data freshness, or geographic coverage scope.

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?

Three sentences with distinct purposes: capability definition, usage trigger, and output description. No redundancy; information is front-loaded and efficiently structured.

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 zero parameters and lack of output schema, description adequately covers purpose, invocation conditions, and return value structure. Could strengthen by specifying geographic/temporal data coverage.

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?

Zero parameters present; baseline 4 per rubric for parameter-less tools. Schema coverage is trivially complete.

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?

States specific verb 'Get' and resource 'drilling intelligence data' with concrete details (active wells, permits issued, completions by region). Implicitly differentiates from sibling opa_get_rig_counts by specifying well/permit data, though lacks explicit sibling comparison.

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?

Provides explicit positive triggers ('Use when the user asks about drilling activity, well permits, or upstream operations'). Lacks explicit 'when-not' guidance or named alternatives, but clear invocation context is provided.

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