get_session_log

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

No annotations are provided, so the description carries the full burden. It describes what is included in the log but does not disclose performance implications, authentication requirements, or side effects. The behavioral disclosure beyond the basic purpose is minimal.

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 well-structured with a purpose statement, background context, and parameter list. It is concise and informative, but the 'Args' section could be slightly more integrated. Overall, it earns its place without unnecessary fluff.

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?

The tool has no output schema, so the description should explain the return format. It says 'full audit log' but does not specify the structure (e.g., fields, ordering). Additionally, it lacks details on pagination or behavior when limit is exceeded. Given the complexity of a log tool, this is incomplete.

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 no descriptions (0% coverage), so the description adds crucial meaning: it explains the session_id parameter (optional, defaults to current session) and the limit parameter (default 100, max 500). This provides clear semantics beyond the raw 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?

The description clearly states it returns the full audit log for an agent session, explaining what is recorded (tool calls, safety checks, blocked attempts). It does not explicitly differentiate from sibling tools, but the purpose is specific and well-defined.

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 description provides context on when to use the tool ('replay exactly what an agent issued during a session'), but does not mention when not to use it or suggest alternatives. No explicit exclusions or comparisons with siblings.

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