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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds real behavioral context by disclosing that only whitelisted fields are honoured and that unknown filters are silently ignored — a critical trait an agent could otherwise misuse. It stops short of describing pagination metadata or return shape.

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 purpose is front-loaded in a single clause, followed by the resource table and then filter syntax — a sensible information hierarchy. The resource list is long and partly restates the enum, but with 28 values it largely earns its space by disambiguating similarly named resources.

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 generic list endpoint it covers the three things an agent needs — resource selection, filter grammar, sort/paging defaults — and no output schema exists, so return-value detail is not required. Minor gap: no mention of what a response envelope or total-count looks like for paging decisions.

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 the baseline would be 3, but the description goes beyond it: it names the full predicate vocabulary (eq, not_eq, cont, start, end, gt, gteq, lt, lteq, in, null) and gives worked filter examples, which the schema only gestures at. The per-resource glosses also add meaning beyond the bare enum strings.

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 and resource scope ('List records from any Fawtar resource, with filtering, sorting and paging') and enumerates the 28 supported resources with one-line semantic glosses, so an agent knows exactly what the tool does. It does not explicitly distinguish itself from siblings such as fawtar_get or fawtar_outstanding, leaving that boundary to inference.

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?

Usage is implied by the resource glosses (e.g. product_unit_types, inventory_levels) which help pick a resource, but there is no explicit when-to-use guidance and no statement of when to prefer fawtar_get over this list tool. No exclusions or prerequisites are given.

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