mirlo_list_calls

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

With no annotations, the description carries full burden for behavioral disclosure. It only states a generic 'List phone calls with filters.' and does not mention read-only nature, authentication requirements, pagination behavior, or what happens when no filters are applied. This is minimally informative for an agent.

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 extremely concise (one sentence), but it is under-specified. While brevity is valued, it sacrifices necessary detail. The sentence earns its place but fails to convey sufficient information.

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 no output schema, no annotations, and 0% schema coverage, the description is inadequate. It does not address pagination, ordering, return format, or error conditions. For a tool with only two simple parameters, the description should provide a clearer picture of its behavior and output.

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 must add meaning. It only says 'with filters' without linking to the parameters (limit, direction). It does not explain that limit controls pagination or that direction filters by inbound/outbound. No additional context is provided beyond parameter names.

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 'List' and the resource 'phone calls', and mentions 'filters' which hints at parameter usage. However, it does not distinguish this tool from sibling tools like mirlo_list_conversations or mirlo_list_tasks, limiting its clarity for an AI agent selecting among similar list tools.

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 is provided on when to use this tool versus alternatives (e.g., mirlo_get_call_transcript for specific calls, or other list tools). The description lacks context about prerequisites, exclusions, or recommended use cases.

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