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

With no annotations, the description carries the full load, and it does disclose that this is a retrieval of a session-scoped snapshot ("today's trading session") and what the response contains field by field. It does not say what happens outside trading hours, how fresh the data is, or whether the values are cached, which are the remaining behavioral gaps.

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?

Three sentences: purpose first, payload second, usage trigger third. The enumeration of return fields is dense but each item earns its place because no output schema exists to carry that information.

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, no-annotation, no-output-schema read tool, the description covers purpose, contents, and when to call it, which is nearly everything an agent needs. Only edge-case behavior (non-trading days, data staleness) is left unaddressed.

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 takes zero parameters and the description correctly introduces none, so there is nothing to mis-specify. Baseline of 4 applies for a no-parameter tool.

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 gives a specific verb and resource ("Retrieves the high-level macro thesis for today's trading session") and then enumerates the concrete payload: Analyst's Take bias, Narrative Risk 1-10, VIX and VVIX climate, and scheduled catalysts. The words "macro" and "general market direction" implicitly separate it from get_symbol_thesis, so an agent can route correctly without opening any 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 states a clear trigger condition: use it when a user asks about general market direction, overall trading conditions, or the morning briefing summary. What's missing is an explicit exclusion or a named alternative (e.g. "for a single ticker use get_symbol_thesis instead"), so the agent must infer the boundary with its siblings.

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