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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that: no mention of what the query can express, how many results come back, or whether the search spans all accounts.

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 short sentence with the core intent front-loaded and no filler. It is efficient, though its brevity contributes to the missing usage and scope detail rather than being a virtue on its own.

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 search tool with no output schema, the description should at least hint at result shape or scope (which accounts/categories, any result limit, ordering). It provides none, leaving an agent unable to predict what comes back or how to phrase constraints.

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% and there is only one required parameter, so the schema does the documenting. The description adds a small nuance by framing the input as free-form natural language rather than structured filters, but that is largely redundant with the parameter name and schema text.

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 (search) and resource (transactions) plus the query modality (natural language), which lets an agent distinguish it from a plain retrieval tool. However, it never contrasts with the obvious sibling list_transactions, so the boundary is left implicit.

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 when-to-use or when-not-to-use guidance at all. With list_transactions, find_anomalies, spending_by_category and spending_by_merchant in the sibling set, an agent gets no help deciding which to pick for a given question.

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