cdr_audit

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

No annotations provided, so description carries full burden. Discloses scanning for specific anomalies and parameter defaults but does not explicitly state read-only nature or potential side effects. Adequate but could be more explicit.

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?

Very concise: a one-line summary followed by clear parameter list. No redundant or extraneous information. Well-structured.

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, parameters, and usage constraints. Output schema exists but description does not detail return values, which is acceptable. Adequate for a scanning tool with moderate complexity.

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 coverage 0%, so description adds meaning: explains ISO timestamps, window cap, defaults, and anomaly detection specifics. Adds value beyond schema titles and defaults.

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 'Scan the acc table for gaps, duplicates, and duration anomalies.' Specifies verb (scan), resource (acc table), and anomalies. Differentiates from siblings like cdr_summary and acc_query_cdrs.

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?

Mentions date window capped at 31 days and advises longer ranges use warehouse/BI tool. Provides explicit context for when to use but does not name alternative tools.

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