sassy_recent_tool_calls

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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates a read-only operation ('Get') from the audit log and provides parameter constraints, but it does not mention ordering, pagination, access requirements, or potential side effects. The provided context is helpful but incomplete.

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 four lines with a front-loaded purpose sentence followed by parameter definitions. Every sentence adds value, and there is no redundant or filler content.

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 low complexity, all three parameters are described, and an output schema exists (so return values need not be explained), the description is nearly complete. It lacks explicit usage exclusions or comparisons to sibling audit tools, which would make it fully self-contained.

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 0%, so the description fully compensates by explaining all three parameters: max_results (with range 1-1000), tool_name (optional filter), and since_minutes (with 0=all). Each parameter gains meaning beyond the bare schema, making the tool usable without guessing.

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 'Get' and the resource 'recent tool call history from audit log', establishing a specific purpose. It distinguishes from sibling audit tools by focusing on 'recent tool calls' rather than the general audit log, but it does not explicitly differentiate itself from alternatives.

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 implies usage through its purpose statement (get recent tool call history) and parameter hints (filter by tool name, time window), but it does not explicitly state when to prefer this tool over siblings like sassy_audit_log or sassy_audit_search. No exclusions or alternative tool mentions are provided.

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