telefonica_analytics_connections_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 states it's a listing operation, implying read-only behavior, but doesn't disclose critical details like authentication needs, rate limits, pagination, or what the output contains. For a tool with no annotations, this is insufficient to guide safe and effective use.

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 in Portuguese that directly states the tool's function. It's front-loaded with the core action and resource, with no wasted words, making it appropriately concise for its purpose.

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 2 parameters with 0% schema coverage, no annotations, but an output schema exists, the description is minimally adequate. It covers the basic purpose but lacks details on parameters, behavioral traits, and usage context. The output schema mitigates some completeness gaps, but overall, it's borderline for a tool in this context.

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 description mentions 'por src_id' and 'de um numero', hinting at the parameters 'src_id' and 'numero_telefone', but it doesn't explain their semantics, formats, or constraints. This adds minimal value beyond the schema's structure.

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 'Lista conexoes de dados moveis de um numero por src_id' clearly states the action ('Lista') and resource ('conexoes de dados moveis'), but it's vague about scope and doesn't differentiate from sibling tools like 'telefonica_list_connections' or 'telematica_analytics_connections_by_device'. It specifies 'de um numero por src_id', which adds some context but remains general.

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 explicit guidance on when to use this tool versus alternatives is provided. The description implies usage for listing mobile data connections for a phone number by src_id, but it doesn't specify prerequisites, exclusions, or compare to similar tools in the sibling list, leaving the agent without clear selection criteria.

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