aureon_list_timeline

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the read-only, paginated nature of the tool and the content categories returned, but says nothing about ordering (e.g., newest-first), authentication requirements, or result shape. It adds some context beyond the name but leaves notable 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?

Two short sentences, front-loaded with what the timeline contains and then the pagination hint. Efficient, though the second sentence overlaps with what the schema already states about 'before' and 'limit'.

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 3-parameter, no-annotation, no-output-schema read tool, the description covers content and pagination adequately but omits ordering and the shape of an event record. It is viable but leaves the agent inferring return structure.

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 all three parameters (limit, before, objectiveId) are already documented in the schema. The description's pagination note largely restates the 'before' cursor semantics without adding format or edge-case detail, so the baseline 3 applies.

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 clear verb+resource ('Timeline of events') and enumerates what populates it (objective changes, executions, health transitions), so an agent knows what it returns. It does not, however, distinguish this from overlapping siblings such as aureon_list_executions, aureon_list_decisions, or aureon_get_audit_trail.

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 only usage instruction is pagination mechanics ('Pass before ... and limit to read the next page'), which is implied usage rather than selection guidance. There is no statement of when to prefer this tool over the executions/decisions/audit-trail siblings, and no exclusions.

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