ts_audit_log

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

Discloses ordering (recent first), scope filtering behavior (client-side with secondary fetch), exclusion of non-device targets, and timeout risk for wide lookbacks. No annotations provided, so description carries burden effectively.

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 short paragraphs, no wasted words. First sentence captures tool purpose, second paragraph explains scope in detail. Efficient and front-loaded.

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 behavior, constraints, filter details, and risks. Output schema exists so return values not needed. Complete for a read-only audit log tool.

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 has 100% coverage, but description adds context: explains scope's client-side filtering and secondary fetch, days timeout risk, and count default/max. Adds value beyond 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?

Clearly states it's a configuration audit log showing who changed what and when, with recent entries first. Distinguishes from sibling tools that deal with devices, users, etc.

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 clear context on when to use optional scope filter and warns about secondary fetch and timeout risks. Lacks explicit comparison to alternatives, but siblings are distinct enough.

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