acc_query_missed

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

No annotations provided, so description must carry full behavioral burden. It omits crucial details such as output format, pagination behavior (limit/offset), side effects, or whether the operation is read-only. Only parameter descriptions are given.

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?

Description is concise with a single-sentence summary and a clear parameter list. Every line adds value, though the parameter formatting could be slightly tighter.

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 complexity (6 parameters, no required params, output schema exists), the description adequately addresses core filters but misses pagination details. Output schema likely covers return values, reducing burden, but behavior around offset/limit is unexplained.

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?

Description adds meaning beyond schema titles: specifies ISO-format for dates and partial match for caller/callee. However, it does not describe limit and offset parameters, which are present in the 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?

Description states 'Query missed calls with optional date range and caller/callee filters,' which is a clear verb+resource. However, it does not explicitly distinguish from the sibling acc_query_cdrs, which likely queries completed calls.

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?

No guidance on when to use this tool versus alternatives like acc_query_cdrs. Missing information about prerequisites or context for querying missed calls.

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