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

Annotations already mark it readOnly and non-destructive, and the description adds meaningful behavior: filter syntax, supported predicates, and the explicit warning that unsupported field predicates are silently ignored. It does not overclaim or contradict the read-only hint.

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 long resource list is justified because all 27 enum values need disambiguation, and the bullet format is scannable. The filter rules are front-loaded before the catalog, and there is no obvious filler, though it is still a sizable wall of text.

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 5-parameter tool with no output schema, the description covers resource selection, filter predicates, sorting, paging, and ignored-field behavior. Minor gaps remain around response shape and pagination metadata, but the required invocation details are present.

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 60%: sort, filters, and resource have descriptions, while page and limit only have schema constraints. The description compensates with a predicate list, filter example, and per-resource meaning for the enum, adding real selection value beyond the schema.

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 leads with a specific verb and resource scope: "List records from any Fawtar resource", then enumerates 27 supported resources with short definitions. This clearly separates it from siblings like fawtar_create and fawtar_get even before inspecting the schema.

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 opening sentence gives clear context: use this when you need to list records with filtering, sorting, and paging rather than creating or fetching a single record. It does not explicitly name alternatives or state when not to use it, so it stops short of 5.

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