aureon_list_reports

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing beyond the implicit read-only nature of 'stored ... reports'. It says nothing about ordering, pagination, filtering, wallet scoping requirements, or whether reports can be empty.

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?

A single short phrase with zero filler, front-loaded with the resource. It is appropriately sized in form, though the sparseness is an under-specification problem rather than a merit.

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 no-parameter list tool with no output schema and no annotations, the description must at minimum convey what a 'report' contains, how results are ordered or bounded, and how it differs from aureon_get_report. None of that is present, so an agent cannot call this confidently alongside its siblings.

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, so per the baseline there is nothing for the description to disambiguate. The scope phrase 'for this wallet' is the only parameter-like context and the implicit wallet binding is at least hinted at.

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 is a bare noun phrase, 'Stored financial reports for this wallet', with no verb indicating the operation (list vs. get vs. prepare). It essentially restates the tool name aureon_list_reports with a scope qualifier, and gives no signal to distinguish it from aureon_get_report, aureon_prepare_report, or aureon_confirm_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?

There is no statement of when to call this tool, no prerequisites, and no mention of alternatives. With four sibling report tools plus aureon_list_timeline and aureon_list_decisions, the absence of any routing guidance leaves the agent to guess.

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