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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so safety is covered. The description only adds the underlying endpoint (GET /payments) and nothing about pagination behavior, whether search and sort combine, or rate limits — useful context but thin against an already-annotated read tool.

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 with no filler and the endpoint tucked at the end. It is efficiently sized, though the parenthetical is slightly ambiguous about whether those are search targets or sortable columns.

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 five-parameter, zero-required read tool with no output schema and full annotation coverage, the description is minimally adequate. It omits the shape of returned records and the interaction between paging, search, and sorting, which an agent would need to call it well.

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 80%, so the schema already documents page, limit, search, and sort_dir; only sort_by lacks a description. The parenthetical hints at sortable/filterable attributes but does not explain how the free-text `search` relates to those fields or which fields it scans, so it adds little 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?

"List or search payments" gives a specific verb pair plus the resource, and the parenthetical enumerates the payment attributes in play (amount, method, date, invoice). This clearly separates it from fieldpulse_get_payment, but it never explicitly says it returns a collection while get_payment returns one record.

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?

"List or search" implies two usage modes and the plural resource implies bulk retrieval, so an agent can infer the list-vs-fetch distinction. However, no alternative is named (fieldpulse_get_payment, fieldpulse_list_invoices) and there are no conditions or exclusions stated for choosing search over paging.

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