aureon_get_full_aureon_loop_flow

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

No annotations are present, so the description carries the full behavioral burden. "Read" implies a safe, non-mutating operation and the filtering constraint (only active objectives with a receipt) is disclosed, but there is no statement of return shape, pagination, or whether it triggers any state change beyond the read.

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 front-loaded sentence with no wasted words. It is dense with jargon rather than explanatory, but it is appropriately sized for the tool.

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?

With no output schema and no annotations, the description is the only source of truth, and it does not explain what a "full AUREON loop" result contains or how the receipt is represented. It scopes the call adequately but leaves the agent guessing about the response.

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 description coverage is 100%, so the schema already documents both parameters, setting the baseline at 3. The description reinforces objectiveId's filtering intent ("active objectives") but adds nothing for the "brief" parameter beyond the schema's own "User brief for teaching shape".

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?

States a specific verb (Read) and resource (full AUREON loop) plus scope (active objectives with a latest execution receipt). It is distinguishable from the sibling aureon_run_full_aureon_loop_demo by the read vs run framing, but the description never names a sibling or defines what the "loop" actually comprises, which is domain jargon.

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?

No when-to-use guidance, no prerequisites, and no routing against the many alternatives in this family (e.g. aureon_run_full_aureon_loop_demo, aureon_get_objective_portfolio_flow, the other get_*_flow tools). The agent must infer applicability entirely from the scope clause.

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