Trace status

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

Annotations only declare readOnly and not-openWorld; the description adds what the annotations cannot: it reads from an in-memory buffer with no I/O, it is instant, it returns an empty buffer when tracing is disabled, and it is batch-safe. It also pre-announces the response shape (trace_status with enabled, file, buffered, recent[]).

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?

Labeled lines (Use when / Avoid when / Speed / Output / Batch-safe) front-load the key gating condition and each line carries distinct information with zero filler.

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?

No output schema exists, but the description enumerates the returned fields (enabled, file, buffered, recent[] with newest last) and covers the disabled-tracing edge case. Nothing an agent needs to call it correctly is missing.

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 coverage is 100% and the single optional `limit` parameter is fully documented with default and max, so the schema carries the load. The description only restates the concept as 'last N' without adding format or behavior detail beyond the schema.

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 and resource: shows the most recent traced tool calls from the in-memory buffer plus the trace configuration. It also implicitly distinguishes itself from the on-disk log by naming VENIRA_TRACE_FILE as the alternative.

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?

Provides explicit 'Use when' (VENIRA_TRACE=1, avoid reading the log file) and 'Avoid when' (tracing disabled, or you need the full on-disk log) conditions, and names the sibling artifact to use instead. Both the positive and negative selection conditions are spelled out.

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