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

No annotations are provided, so the description carries the full burden. It usefully discloses the default scope (last 30 days, 50 items) and the return-field set, which matters with no output schema. It says nothing about permissions, how filters combine, or how pagination interacts with the defaults, leaving notable gaps for a 14-parameter query 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?

Three short sentences with no filler, front-loaded with the core purpose. The return-field enumeration is a little list-like but each item is informational, so little is wasted.

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?

Given 14 optional parameters and no output schema, listing return fields is a valuable addition, and defaults are covered. Still missing are how multiple filters combine, the search field's scope beyond the schema note, and any indication that results are paginated via offset.

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 100%, so every filter, its unit, and its default is already documented in the schema. The description's reference to date filters and defaults merely echoes startDate/endDate/limit without adding syntax or semantics 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?

States a specific verb+resource ("Search and filter transactions") and enumerates the returned fields, so the agent knows exactly what kind of tool this is. However, with ~80 siblings including get_expenses_for_period, get_cash_flow, and get_spending_by_categories, it offers no differentiation from other transaction-read tools.

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?

"Use date filters to limit results" is a usage hint, not a when-to-use rule, and the default window/size is behavioral context rather than guidance. No alternatives are named and no exclusions are given, despite several sibling tools that also return transaction data.

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