get_freight_rate_pressure

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

Discloses return contents: current values, week-over-week changes, z-score, trade corridor mapping, and scoring interpretation. Adds context beyond empty 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?

Well-structured, front-loaded with main function, followed by explanatory details. Each sentence contributes useful information.

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 describes output for a 0-parameter tool without output schema. Could mention data refresh frequency for full completeness.

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?

No parameters; schema coverage 100%. Description adds value by explaining indices and scoring beyond schema.

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?

Clearly states it returns freight rate pressure scores for WCI and SCFI indices, defining indices and scoring scale. Distinguishes from siblings by focusing on container shipping pressure.

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?

Explicitly states 'Use to assess freight cost pressure on specific trade lanes.' No alternatives mentioned, but purpose is clear given no parameters.

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