nexo_continuity_audit

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

Without annotations, the description carries the full burden of behavioral disclosure. It only states the tool returns a timeline, implying a read operation, but provides no information about side effects, permissions, or computational intensity. Key behavioral traits are missing.

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 a single sentence, which is concise, but it lacks sufficient detail. It is minimal without being informative. Front-loading is fine, but value per sentence is low.

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?

Given the tool's specialized purpose (forensic continuity timeline), the description is far too brief. It does not explain what the timeline contains, how results are ordered, or what constitutes a continuity event. No output schema exists to compensate.

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 has two parameters (conversation_id, limit) with zero description coverage. The tool description does not explain their purpose or how they influence the output. For example, 'limit' likely caps the timeline length, but this is not stated.

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 clearly states the verb 'return' and resource 'forensic continuity timeline' for a conversation, making the tool's primary function evident. However, it does not explicitly distinguish from sibling continuity tools like nexo_continuity_snapshot_read, but the name 'audit' implies a different operation.

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 guidance is given on when to use this tool versus alternatives such as nexo_continuity_snapshot_read or nexo_continuity_compaction_event. The description lacks any context on prerequisites or situational fit.

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