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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered and the description only needs to add operational context. It adds the endpoint (GET /transfers/search) but says nothing about how multiple criteria combine (AND vs OR), whether matching is case-insensitive or substring, or how results are ordered by default — the 'and/or' phrasing actively leaves combination semantics ambiguous.

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 sentences with no filler; the searchable fields and the date-range capability are front-loaded before the endpoint reference. Nothing repeats the annotations or the schema.

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 six-parameter, all-optional search with full schema documentation and no output schema, this covers what to search on and the endpoint. The remaining gap is behavioral: how criteria combine and how results are sorted/paginated is left entirely to the schema's per-parameter notes.

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 baseline is 3, but the description genuinely adds meaning the schema lacks: the opaque `query` parameter ('Text to match') is explained as matching token, description, amount or recipient details. It does not clarify the interaction between query and start_date/end_date, but it earns credit above baseline.

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 ('Search transfers') plus the fields the search covers, which is more than a restatement of the name. It does not explicitly contrast itself with the sibling pinpayments_list_transfers, so an agent must infer that search is the criteria-driven path and list is the unfiltered path.

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 'Search transfers by token, description, amount or recipient details and/or a created-date range' — use it when you have match criteria. There is no explicit when-not, no mention of when to prefer pinpayments_list_transfers instead, and no statement about prerequisites or empty-result behavior.

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