telefonica_analytics_portability_by_number

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 mentions listing events, which suggests a read-only operation, but doesn't specify permissions, rate limits, output format, or pagination. This leaves significant gaps in understanding how the tool behaves beyond its basic function.

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 that directly states the tool's function without unnecessary words. It's front-loaded with the core action, making it easy to parse, though it could be slightly more informative without sacrificing brevity.

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 with two required parameters), no annotations, and the presence of an output schema, the description is minimally complete. It covers the basic purpose but lacks details on behavior, usage context, and parameter specifics, making it adequate but with clear gaps for effective agent use.

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 minimal semantics by indicating that parameters are used to list events 'por src_id' and 'de um numero', but with 0% schema description coverage and two required parameters, it doesn't fully compensate. It hints at the purpose of 'src_id' and 'numero_telefone' but lacks details on formats or constraints, resulting in an adequate but incomplete explanation.

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 action ('Lista eventos de portabilidade') and resource ('de um numero por src_id'), which clarifies the tool's purpose. However, it's somewhat vague about what 'eventos de portabilidade' entails (e.g., portability events like transfers or changes), and it doesn't differentiate from sibling tools like 'telefonica_list_portability_events', leaving room for confusion.

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, such as 'telefonica_list_portability_events' or other analytics tools. The description implies usage for listing events by number and src_id, but it lacks explicit context, prerequisites, or exclusions, offering minimal direction for selection.

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