get_prices_by_date_global

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only mentions the Pro+ subscription requirement, but does not describe return format, pagination, or whether the operation is read-only (though 'get' implies it). This is minimal behavioral context.

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 a single sentence that efficiently conveys both the purpose and the access requirement. No filler or redundancy.

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 tool with one optional parameter and no output schema, the description covers the essential purpose and requirement. However, it lacks explicit guidance on when to use this over similar price tools, and could mention return format. Still, it's adequate for a basic retrieval tool.

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?

Schema coverage is 100% with the 'date' parameter fully described (format and default). The description adds no additional parameter semantics, which is acceptable given that the schema does the heavy lifting. Baseline 3 applies.

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 uses a specific verb ('Get') and resource ('stock prices') with a clear scope ('all Global instruments on a specific date'). This clearly distinguishes it from sibling tools like get_prices_by_date (likely non-global) and get_latest_prices_global (latest vs. specific date).

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 clearly states the context for use: global instruments on a specific date. It does not explicitly mention alternatives or exclusions, but the scope is well-defined. The subscription requirement adds a prerequisite, which helps agents decide if they can use it.

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