getCOTList

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

Annotations already indicate readOnlyHint, idempotentHint, and openWorldHint. The description adds little beyond stating the tool provides a 'comprehensive list' and uses an API. No behavioral details such as pagination, response format, or update frequency are disclosed. Description does not contradict 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 composed of two succinct sentences. The first sentence conveys the core purpose, and the second adds context about the API and market segments. It is front-loaded and contains no superfluous 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?

The tool has no parameters and no output schema. The description explains what data is accessible but does not describe the return structure or how to interpret the list. For a simple listing tool, it is adequate but leaves the agent without details on the output format.

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?

With zero parameters and schema coverage at 100%, the description does not need to elaborate on parameter semantics. The mention of 'by commodity or futures contract' implies possible filtering but the schema has no properties, so the description is consistent and adds no confusion.

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 states the tool's purpose: 'Access a comprehensive list of available Commitment of Traders (COT) reports by commodity or futures contract.' It uses a specific verb ('access'), identifies the resource ('list of COT reports'), and differentiates from sibling tools like getCOTAnalysis and getCOTReports by focusing on the list.

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?

The description provides no guidance on when to use this tool versus its siblings. It does not mention any prerequisites, exclusions, or contexts where alternative tools (e.g., getCOTReports) would be more appropriate. The lack of guidelines leaves the agent to infer usage from the tool name alone.

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