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

Annotations already mark this as read-only and idempotenttarifa. The description adds meaningful context by specifying exactly what data categories are exposed, which is especially valuable without an output schema. No contradiction with annotations.

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?

A single, front-loaded sentence lists the full set of contact data with no filler or repetition. Every phrase contributes to an agent's understanding of the tool's scope.

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 zero parameters, strong annotations, and no output schemaeb, the description serves as a complete output specification: it names every category of contact data the tool can provide. No essential information for invoking it correctly is missing.

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 tool has zero parameterseb, so parameter semantics are trivially satisfied. The description does not need to clarify inputs, and the baseline of 4 for a no-parameter tool is appropriate.

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 identifies the resource and enumerates its contents: phone, support schedule, department emails, non-stop channels, address, and fiscal data. It distinguishes the tool from siblings like clickphone_tarife or clickphone_pachete, though it lacks an explicit verb such as 'returns' or 'provides'.

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 described content strongly implies when to use it: whenever contact information or support channels are requested. It does not explicitly name alternatives or exclusion criteria, but the domain is clear enough for an agent to route correctly.

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