macro_shipping_bcti

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds a source URL and a return type (pandas.DataFrame), which provides some context beyond the title, but does not disclose additional behavioral traits such as data frequency, date ranges, or potential parse failures. No contradiction with annotations.

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 very short and front-loaded with the key identifier (BCTI), followed by a source URL and return type. However, the ':return:' line partially repeats the title, making it slightly redundant. Still, the structure is efficient and not verbose, earning a strong score.

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 zero-parameter tool, the description is mostly adequate, but it lacks details about the DataFrame's contents, such as columns, time range, or update frequency. The URL provides a hint about the data source, and the return type is stated, but without an output schema, more descriptive detail would help the agent understand what data is returned. Slightly below the higher end due to this gap.

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 tool has zero parameters, so the description is not required to explain parameter semantics. The baseline of 4 applies because no parameters exist and the description correctly implies no input is needed.

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 identifies the resource as the refined oil transportation index (BCTI) and states it returns that index via the ':return:' line. Although no explicit verb like 'fetch' or 'get' is used, the resource is specific and distinct from the many shipping/macro sibling tools. Lacks explicit differentiation from siblings, but the name and return statement make the purpose reasonably clear.

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?

No guidance is provided on when to use this tool versus alternatives such as macro_shipping_bdi, macro_shipping_bpi, or macro_shipping_bci. The description does not mention any context, exclusions, or alternatives, leaving the agent without decision support for tool selection.

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