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

No annotations are provided, so the description carries the full burden. It discloses the report contents (snapshot metrics, all signals, summary, provenance), which gives an idea of the response. However, it does not explicitly state read-only behavior, response format, or error handling, leaving some 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?

The description is one sentence, front-loaded with the core purpose ('Full Orion report for a specific date'), and then enumerates the contents. There is no wasted text.

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 simple retrieval tool with one parameter and no output schema, the description sufficiently conveys what the tool does and what data it returns. It could mention the response format explicitly, but the listed contents are enough for an agent to make a reasonable judgment.

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 covers the single 'date' parameter with 100% coverage, including format and a pointer to list_reports. The description repeats the date format but adds no additional semantics beyond the schema, so the baseline 3 is appropriate.

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 states 'Full Orion report for a specific date' followed by the included contents (snapshot metrics, all signals, summary, provenance). This clearly identifies what the tool returns and differentiates it from siblings like get_signals (which likely returns only signals) or get_daily_brief (a brief, not a full report).

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 implies when to use it: when you need the full report for a specific date. The schema's date property adds 'see list_reports for available dates', which hints at a workflow. However, there is no explicit comparison with alternatives like get_signals or get_daily_brief, so exclusions are absent.

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