wa_audit_tail

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

States 'Read-only' and explains that message bodies are stored as preview+hash only. With no annotations, description effectively discloses safety and data constraints.

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 concise sentences. Front-loaded with purpose. No redundant or extraneous text.

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, read-only nature, and data storage. However, lacks explanation for the 'limit' parameter, which is significant given its optionality and default. Output schema exists but parameter semantics are left unaddressed.

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 only parameter 'limit' has no schema description (0% coverage). The description does not mention or clarify the parameter, leaving the agent to assume its function.

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?

Clear verb 'Return' and specific resource 'send-attempt audit records' with filtering by allowed/blocked/failed. Distinguishes from sibling tools (sending or listing recipients).

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?

Implies usage for audit records but does not provide explicit when-to-use or alternatives. No guidance on when not to use this tool in favor of siblings.

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