Get economic calendar

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description only needs to add extra behavioral context. It does so by specifying the forward-looking 14-day window and listing the data fields (forecast, prior value, expected market impact), which goes beyond the annotation metadata.

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 exactly two sentences: the first states what the tool returns, the second explains when to use it. Every word earns its place, and key facts are front-loaded.

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?

Given the tool has no parameters and no output schema, the description sufficiently covers what data is returned (forecast, prior, impact), the time window (~14 days forward), and the primary use case (flagging macro events). This is complete for a simple, read-only calendar 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?

The tool has zero parameters, so the baseline is 4. The description doesn't need to explain parameters, but it enriches the tool's behavior by describing the calendar's content and time range, which is useful for an agent.

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 provides a forward (~14 day) economic calendar with scheduled releases, forecast, prior value, and market impact. This specific verb+resource+scope is distinct from sibling macro tools like stoquant_get_macro_indicator or stoquant_get_macro_dashboard, which focus on individual indicators or broader dashboards.

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 explicitly says 'Use to flag upcoming macro events (CPI, FOMC, jobs) that could move positions,' giving a clear when-to-use context. It does not mention alternatives or exclusions, so it stops short of a 5, but the intended use case is well understood.

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