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

Annotations already declare readOnly/openWorld/destructive, but the description goes well beyond them: read-only and no account needed, three return renderings (structured content, markdown card, PNG image), error behavior for out-of-window dates, and nuanced point-in-time semantics including the specific rows that are not point in time and the point_in_time_note. That is substantial disclosure the annotations cannot carry.

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 opening sentence and the card enumeration are front-loaded and every clause carries substantive information about badges, rows, and dated reads. It is, however, long and somewhat prose-heavy, and the explanation of the three return renderings partially duplicates the output schema, costing a point on tightness.

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 high-complexity, multi-card tool with an output schema and clean annotations, the description covers purpose, routing, dated-read semantics, caveats, and error behavior. Nothing an agent needs to invoke it correctly is missing.

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% and the single as_of parameter is documented, yet the description adds real meaning beyond it: the 365-day reach, exclusion of today as the default, the error on future/too-old dates, rules_note behavior, per-row point_in_time, and the Investment card's Data centres/Chips exception. This is more than the schema conveys.

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 names a specific resource (the Jawz Dashboard) and enumerates exactly what it contains: six readings (Regime, Money, Business cycle, Financial conditions, Store of value, Investment) with their badge vocabularies and per-card rows. It explicitly differentiates itself from sibling detail tools (get_macro_regime, get_financial_conditions, get_growth_indicators, get_inflation_indicators, get_indicator_history), so an agent can route correctly without opening a schema.

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?

It clearly routes: this tool gives the overview, while the named siblings give 'the detail behind the cards' and get_indicator_history gives a card or row over time. It also states when as_of applies and its constraints. It does not spell out explicit exclusions beyond the date-window error, so it falls just short of a 5.

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