OilPriceAPI

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

No annotations provided, so description carries full burden. It discloses the specific return fields (oil rigs, gas rigs, total count, week-over-week change) and notes 'No parameters needed', which adequately covers behavior for a simple retrieval tool. Could mention data freshness/frequency.

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?

Four sentences, front-loaded with the core action. Each sentence serves distinct purpose: data source, usage trigger, return values, and parameter requirements. Zero redundancy, excellent information density.

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?

Despite lacking an output schema, the description explicitly documents the return structure (specific fields returned). Combined with usage guidance and parameter confirmation, this is complete for a simple retrieval tool with no inputs.

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 required. Schema coverage is 100% (vacuously true). Description explicitly states 'No parameters needed', confirming the schema structure. Baseline 4 achieved per instructions for 0-param tools.

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 the specific action (Get), resource (US oil and gas rig count data), and authoritative source (Baker Hughes). It distinguishes from sibling opa_get_drilling by specifying the exact data provider and return structure.

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 guidance ('Use when the user asks about drilling activity, rig counts, or oil field operations'). Lacks explicit named alternatives or negative constraints (e.g., 'do not use for historical trends, use opa_get_history instead'), but context is clear.

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