get_now

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only describes the data returned but does not mention whether the tool is read-only, requires authentication, has rate limits, or any side effects. This is a significant gap for a tool that presumably makes multiple backend requests.

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 two sentences, each earning its place. The first front-loads the purpose with clear noun phrases, and the second quantifies the value proposition. No redundant or filler content.

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 zero parameters, no annotations, and an output schema present (so return values are documented elsewhere), the description adequately covers the tool's purpose and scope. It lists the categories of information retrieved, which is sufficient for a parameterless combined-fetch 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 input schema has zero parameters and 100% schema coverage, so the description does not need to add parameter details. The description adds value by explaining what the tool returns (exchange status, volatility, economic events, data health), which is helpful beyond the empty 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?

The description clearly states the tool retrieves a composite of current world state data: exchange status, volatility metrics, economic event countdowns, and data health. The phrase 'One call replaces 4-6 separate API calls' distinguishes it from sibling tools like get_exchanges or get_volatility which are individual endpoints.

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 states this tool replaces multiple separate API calls, indicating it should be used for a broad overview. However, it does not mention when NOT to use it or provide explicit alternatives, relying on the implied context that siblings exist for specific subsets.

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