get_temporal_context

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

With no annotations provided, the description carries full burden. It adequately discloses what data is returned (days since halving, cycle phase, analogs, guidance) but omits operational characteristics like whether this is a read-only operation, rate limits, or data freshness/staleness.

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?

Single dense sentence with zero waste. Front-loaded with action verb ('Get'), followed by resource specification, then colon-delimited list of specific return components.

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 zero-parameter tool without output schema, the description sufficiently enumerates return value components (days, phase, analogs, guidance). Minor gap: does not indicate if tool covers only Bitcoin or if it retrieves data for other assets with halving mechanics.

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?

Zero parameters present; baseline 4 applies per rubric. No parameter explanation required or provided.

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?

Excellent specificity: 'Get Bitcoin halving cycle positioning' uses concrete verb and resource, clearly distinguishing this from sibling tools like get_historical_context or get_macro_context by focusing specifically on halving cycle data rather than general price history or macro indicators.

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?

Provides no guidance on when to invoke this tool versus alternatives like get_historical_context or get_asset_context, nor does it specify prerequisites (e.g., Bitcoin-only analysis scope).

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