audit_session

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

No annotations provided, so description carries full burden. It mentions the checks and output decision but does not disclose whether the operation is read-only or has side effects, nor any required permissions. Somewhat opaque.

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 efficient sentences: first states purpose, second adds prerequisite and details. No wasted words, front-loaded with key action.

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?

Covers purpose, number of checks, prerequisite, and decision type. However, without an output schema, the description does not detail the structure of the returned decision (e.g., object fields), which would be useful for invocation.

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?

Only one parameter (session_id) with full schema coverage (100%). The description adds no additional meaning beyond what the schema already provides ('Session ID to audit').

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?

Description clearly states it audits a Direct session's changes, performs 16 deterministic checks, and returns a decision. It distinguishes from sibling tools like audit_task (different resource) and safe_audit (likely a safe variant).

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?

Explicitly states the prerequisite that the session must be finalized first. However, it does not contrast with alternative audit tools like safe_audit_direct_session, leaving the agent to infer when to use this one.

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