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

The readOnlyHint=true annotation already establishes this is a safe read, lowering the burden. The description adds the useful nuance that response/resolution times are reported both with and without business hours, but says nothing about pagination, result volume, or permission requirements. With annotations covering the safety profile, this is adequate but not rich.

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 that lists the metrics, followed by a short API endpoint mapping. Nothing is padded. The 'Trengo: GET /reporting/agent_performance' clause is mildly redundant but useful for endpoint identification.

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?

With no output schema, the description's enumeration of returned metrics does valuable work in telling the agent what comes back. The 7 filter parameters are covered by the schema. The only gap is behavioral detail (pagination, date-range semantics), which is minor for a read-only reporting endpoint.

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 100%, so the schema fully documents all seven parameters, including the paired start_date/end_date constraint. The description adds no parameter-level meaning beyond this, so the baseline of 3 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 names the specific resource (per-agent performance) and enumerates the exact metrics returned: messages sent, notes, tickets assigned/closed, first response and resolution times. An agent immediately knows what the tool produces. It does not, however, distinguish itself from reporting siblings such as trengo_get_reporting_metrics or trengo_get_ticket_details_report.

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?

There is no explicit guidance on when to use this tool versus the other reporting tools in the sibling list, nor any stated prerequisites. The phrase 'over a period' weakly implies a date-scoped reporting call, but the agent must infer this. No exclusions or alternatives are mentioned.

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