telefonica_analytics_locations_by_number

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

No annotations are provided, so the description carries the full burden. It mentions listing a timeline, implying a read-only operation, but doesn't disclose behavioral traits such as whether it requires specific permissions, rate limits, pagination, or what the output format looks like. The description is too brief to provide meaningful context beyond the basic action.

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 in Portuguese that directly states the tool's function. It's front-loaded with the core action, though it could be more structured by including parameter hints or usage context.

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's an output schema (which reduces the need to describe return values) but no annotations and 0% schema coverage for parameters, the description is incomplete. It covers the basic purpose but lacks details on parameters, usage, and behavioral context, making it only minimally adequate for a tool with two required parameters.

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 schema provides no parameter descriptions. The tool description doesn't mention any parameters or their semantics (e.g., what 'src_id' and 'numero_telefone' represent). This leaves both parameters undocumented, failing to compensate for the lack of schema coverage.

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 lists a timeline of locations by number for voice and connections, which provides a basic purpose. However, it's somewhat vague about what 'timeline of locations' means and doesn't differentiate from sibling tools like 'telefonica_analytics_connections_by_number' or 'telefonica_analytics_phones_by_antenna' that also deal with phone number analytics.

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. The description mentions 'voz + conexoes' (voice + connections), but it doesn't specify if this is for historical tracking, real-time data, or how it differs from other telefonica_analytics tools that also handle phone numbers and connections.

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