Fetch in- and outbound faxes

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the 'Read-only' line mostly restates structured data. The endpoint reference (GET /faxes) adds a small amount of context, but nothing is said about pagination behavior, default ordering, or result volume.

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?

Two short clauses, front-loaded with the operation, no filler. It is perhaps too terse — the 'Read-only' clause is redundant given annotations — but there is no wasted verbiage.

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?

For a 7-parameter list tool with no output schema, the description is minimally adequate: the agent knows it lists faxes and is read-only, and the schema covers parameters. It omits pagination/return-shape expectations and any disambiguation from sibling fax tools, so it is complete but thin.

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 coverage is 100%, so all seven parameters (page, per_page, order, filters, response_format) are already documented in the schema. The description contributes nothing parameter-specific, which is acceptable at baseline 3 but adds no extra value.

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?

States a specific verb (fetch) and resource (in- and outbound faxes), plus the underlying endpoint GET /faxes. It's clear this is the list operation versus siblings like placetel_get_fax, placetel_create_fax, and placetel_delete_fax, though it never names those alternatives explicitly.

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 on when to use this versus placetel_get_fax (single) or the other fax tools. The 'in- and outbound' phrase hints at scope, but there are no exclusions, prerequisites, or alternative routing, leaving the agent to infer selection from the name alone.

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