OilPriceAPI

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

No annotations provided, so description carries full disclosure burden. It successfully adds critical operational constraints ('Requires a paid plan with energy intelligence access') and return structure ('Returns country-level production figures') not inferable from schema. Could enhance with data frequency or rate limits.

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, each earning its place: purpose, usage trigger, return format, and access requirements. Information is front-loaded with no redundancy or filler.

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?

Adequately covers the zero-parameter tool's scope despite lacking output schema, specifying country-level granularity and access restrictions. Minor gap regarding data update frequency or specific member countries covered.

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?

Input schema contains zero parameters (empty object), triggering baseline score of 4 per rubric. No parameter clarification needed or provided.

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 opens with specific verb-resource pair ('Get the latest OPEC oil production data') and clearly distinguishes from siblings by specifying OPEC/OPEC+ scope versus general price, futures, or drilling data available in other 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?

Provides explicit positive guidance ('Use when the user asks about OPEC output, production quotas, supply cuts, or OPEC+ compliance') covering multiple query variants. Lacks explicit 'when not to use' or sibling alternatives, but the specificity effectively guides selection.

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