telefonica_analytics_distinct_numbers_by_case

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the counting action without detailing output format, pagination, rate limits, authentication needs, or whether it's read-only or destructive. This is inadequate for a tool with an output schema but no annotation coverage.

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, efficient sentence with no wasted words. It's front-loaded with the core action, making it easy to parse quickly.

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 (analytics function with one parameter and an output schema), the description is minimally complete. It states the purpose but lacks behavioral details and usage guidelines. The presence of an output schema reduces the need to explain return values, but without annotations, more context on operation traits is warranted.

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 description adds meaning by specifying that 'src_id' is used to count distinct numbers by case, which clarifies the parameter's role beyond the schema's minimal title. With 0% schema description coverage and only one parameter, this compensates adequately, though it could provide more context on what 'src_id' represents.

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 states the tool counts distinct numbers of origin and destination by src_id, which clarifies the verb ('conta' - counts) and resource (distinct numbers). However, it's vague about what 'origem e destino' (origin and destination) specifically refers to in this context (e.g., phone calls, messages), and it doesn't differentiate from sibling tools like 'telefonica_analytics_distinct_numbers_by_file'.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, exclusions, or compare it to similar tools such as 'telefonica_analytics_distinct_numbers_by_file', leaving the agent without context for selection.

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