b24_telephony_calls

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

No annotations are present, so the description carries full burden for behavioral disclosure. It does not mention that the tool is read-only, any authentication needs, or performance considerations like pagination. The description only states it lists calls, which is minimal.

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 a single concise sentence that front-loads the verb 'Lista' (Lists). It is efficient with no wasted words, though it could benefit from structural elements like bullet points for clarity.

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 that there is no output schema and the tool has 3 parameters (including a nested object filter), the description is incomplete. It does not explain the return format, pagination behavior, or how the optional parameters like 'select' and 'webhook_url' affect the 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 coverage is only 33% (only 'filter' has a description in schema). The tool's description adds meaning by listing filterable fields (CRM entity, user, duration, date), which corresponds to the 'filter' parameter. However, it does not explain 'select' or 'webhook_url' parameters, leaving gaps.

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 tool lists call history with filters by CRM entity, user, duration, and date. This distinguishes it from sibling tool b24_call (which likely makes calls) but not from other listing tools like b24_crm_list.

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, such as when to use b24_crm_list instead. No when-not or exclusion criteria provided.

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