macro_shipping_bci

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds only a data source URL and return type, but no behavioral context such as data scope, update frequency, or limitations. 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 extremely short and compact, but the structure is fragmented, mixing a raw URL with docstring-style :return: and :rtype: lines. It is not poorly sized, but the format is not polished.

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 zero-parameter data retrieval tool, the description does not specify whether the data is historical or current, what columns are present, or the time range. The presence of an output schema would mitigate this, but there is none, so the description carries the full burden and falls short.

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, and the baseline for this case is 4. The description correctly notes the return type and does not need to explain parameters.

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 tool's resource as the Capesize Freight Index (BCI) and indicates it returns a pandas DataFrame. It distinguishes itself from sibling shipping tools by naming the specific index, though it lacks an explicit verb like 'fetch' or 'get'.

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?

There is no guidance on when to use this tool versus alternatives such as macro_shipping_bdi, macro_shipping_bpi, or macro_shipping_bcti. The description does not mention any context, prerequisites, or exclusions.

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